Skip to main content
返回工作区
OpenClaw第 5 个文件,共 8 个 · 4 个字段

TOOLS.mdHow & when to use tools

Governs which external tools and APIs the agent can call, under what conditions, and with what constraints — preventing runaway API usage.

此文件控制什么

TOOLS.md 管理你的智能体在技术上能做什么——它可以调用哪些外部工具和 API、在什么条件下调用、以及有什么约束。没有 TOOLS.md,拥有工具访问权限的智能体会通过随机调用烧掉 API 配额、访问不应该看到的数据,或者在没有安全措施的情况下尝试可能产生现实后果的操作。

运行时在 AGENTS.md 之后加载 TOOLS.md,并用它来构建工具权限层。将其视为安全策略:AGENTS.md 定义智能体应该做什么;TOOLS.md 定义它在技术上被允许做什么。这两个文件之间的差距就是你的攻击面。

安全优先的配置原则是:从零访问权限开始,只添加 AGENTS.md 所需的权限。每个工具权限都应该由 AGENTS.md 中的特定步骤来证明其合理性。如果某个工具未在任何 AGENTS.md 步骤中引用,它就不应出现在 TOOLS.md 中。这种零访问基线可以防止随着智能体范围扩展而出现的能力蔓延。

为什么重要: Without TOOLS.md, agents burn through API quotas with random invocations.

逐字段详解

定义智能体行为的 4 个字段

toolRules必填

When and why each tool should be invoked.

toolRules: "e.g. Only call search API when user asks a factual question..."
envConfig可选

Environment variables and configuration the tools depend on.

envConfig: "e.g. API_KEY stored in .env, rate limit: 100/hour..."
toolConstraints必填

Hard limits on tool usage to prevent misuse.

toolConstraints: "e.g. Max 3 API calls per turn, no writes to production DB..."
fileConventions可选

File naming and storage conventions tools must follow.

fileConventions: "e.g. Logs go to /tmp/agent-logs/, use ISO 8601 dates..."

实际配置示例

FinleyManchester · 8 人 · 会计事务所
## toolRules
- Use GOV.UK search only for HMRC guidance and legislation lookups
- Use the client database in read-only mode for matter references
- Use Slack API for posting research summaries to #tax-queries only
- Never call any tool without a clear connection to the current research query

## envConfig
- GOV_UK_API: configured via environment variable (never hardcode)
- CLIENT_DB: read-only connection string via .env
- SLACK_BOT_TOKEN: scoped to #tax-queries channel only

## toolConstraints
- Maximum 5 GOV.UK API calls per query to prevent rate limiting
- Client database: SELECT queries only, no INSERT/UPDATE/DELETE
- Never expose raw API responses to users — always summarise
- No access to client financial records (UTRs, bank details, NI numbers)

## fileConventions
- Research outputs saved to /research/[client-ref]/[date]-[topic].md
- Use ISO 8601 dates in all filenames
- Never include client PII in filenames

常见错误

在没有 TOOLS.md 的情况下使用完整工具权限

拥有工具访问权限但没有 TOOLS.md 的智能体具有不受限制的能力。它们会随意调用每个可用工具,烧掉配额并可能访问敏感数据。务必定义明确的工具规则。

在 envConfig 中放入实际 API 密钥

envConfig 应该引用环境变量名,而不是实际的密钥。硬编码在 TOOLS.md 中的密钥会出现在版本控制、日志中,甚至可能出现在智能体的对话输出中。

toolConstraints 与 AGENTS.md 的任务要求冲突

如果 AGENTS.md 要求智能体更新客户记录,但 TOOLS.md 将数据库限制为只读,智能体会静默失败或自行发明变通方法。两个文件需要一起审计。

对写入文件的智能体未设置 fileConventions

没有约定时,智能体会创建名称不一致、位置不可预测、没有日期标记的文件。这使得输出无法查找和审计。

SetupClaw 如何处理

安全是起点。我们的部署专家会对照 AGENTS.md 的任务范围审计每项工具能力,应用最小权限默认配置。只有 AGENTS.md 特定步骤所需的工具才会被启用,约束条件根据你的数据敏感性要求进行校准。

£770

TOOLS 与 AGENTS 范围的安全审计 + 最小权限配置 + 22 项安全检查清单

£1,100

以上全部 + 分阶段能力发布的工具沙箱 + 预发布/生产环境分离

£2,200

以上全部 + 环境特定配置 + 自动化安全回归测试

  • 全部 4 个字段已配置,采用安全优先的默认值
  • 22 项安全审计已完成并记录在案
  • 工具权限已对照 AGENTS.md 步骤进行论证
  • 环境变量已记录(无硬编码密钥)
  • 所有智能体输出的文件命名约定已建立

安全审计和配置在第 1-2 天完成。沙箱化发布在第 5 天完成(Standard+)。

进阶主题

分阶段能力发布的工具沙箱

不要一次性启用所有工具,而是使用分阶段发布模式。从只读访问开始,监控一周,然后逐步启用写入能力。TOOLS.md 支持 sandboxed 字段,该字段将工具访问限制在预发布环境中,直到明确提升到生产环境。

## toolConstraints
- PHASE 1 (week 1-2): Read-only access to Shopify, Slack monitoring only
- PHASE 2 (week 3-4): Add Slack posting to #customer-support
- PHASE 3 (month 2+): Add carrier tracking API access
- ROLLBACK: If error rate exceeds 5%, revert to previous phase

配置示例

Persona AMeridian首席参谋

# TOOLS.md -- Tool Rules

## toolRules
- Confirm attendees before scheduling any calendar event
- Use approved templates for all external communications
- Notion: read and update project boards; never delete pages
- Gmail: draft emails for review; never send without confirmation

## envConfig
- Notion API, Slack API, Gmail API, Google Calendar API
- All keys configured via environment variables

## toolConstraints
- No external emails without draft review by the principal
- No public document creation without explicit approval
- Calendar: read all; create/modify only for the principal’s calendar

## fileConventions
- Meeting notes: /meetings/[date]-[topic].md
- Action plans: /actions/[date]-[initiative].md
- Status reports: /reports/[week]-status.md
Persona BAxiom (增长黑客)
# TOOLS.md -- Tool Rules

## toolRules
- Date-range bounds on all analytics queries (max 90 days)
- Use Python for statistical analysis and significance testing
- Mixpanel for funnel analysis; PostgreSQL for cohort queries
- Google/Meta Ads: read-only access for campaign performance data

## envConfig
- Mixpanel API, PostgreSQL (read-only), Google Ads API, Meta Ads API
- All keys configured via environment variables

## toolConstraints
- No modifying live experiments or ad campaigns
- No production PII access — use anonymised datasets only
- Maximum 20 analytics queries per session
- No budget allocation changes without escalation

## fileConventions
- Experiment briefs: /experiments/[date]-[hypothesis].md
- Post-mortems: /experiments/[date]-[hypothesis]-results.md
- Growth playbook updates: /playbook/[topic].md
Persona CLumen (科研人员)
# TOOLS.md -- Tool Rules

## toolRules
- Publication date filters on all database searches (default: last 5 years)
- Cross-reference at least 2 sources before including in synthesis
- PubMed for biomedical literature; Google Scholar for broader search
- Zotero for citation management and bibliography generation

## envConfig
- PubMed API, Google Scholar API, Zotero API
- All keys configured via environment variables

## toolConstraints
- No summarising abstracts as if they were full papers
- Flag all preprints and non-peer-reviewed sources explicitly
- Maximum 25 search queries per research session
- Never cache full-text articles locally

## fileConventions
- Literature reviews: /research/[topic]/[date]-review.md
- Evidence tables: /research/[topic]/[date]-evidence.md
- Bibliographies: /research/[topic]/bibliography.bib
Persona DNarrative (内容创作者)
# TOOLS.md -- Tool Rules

## toolRules
- SEO tools (Ahrefs) for keyword research and intent analysis only
- Match posting times to platform-specific engagement windows
- WordPress for content management; Buffer for social scheduling
- ConvertKit for email list management; GA4 for performance tracking

## envConfig
- WordPress API, Ahrefs API, Buffer API, ConvertKit API, GA4 API
- All keys configured via environment variables

## toolConstraints
- No direct publishing to any platform — always draft and queue
- No auto-send emails without human review
- No competitor names in content without legal review
- Maximum 10 SEO tool queries per content piece

## fileConventions
- Content briefs: /content/briefs/[date]-[slug].md
- Drafts: /content/drafts/[date]-[slug].md
- Performance reports: /content/reports/[month]-performance.md
Persona EArchitect (首席工程师)
# TOOLS.md -- Tool Rules

## toolRules
- Run linter before executing any code changes
- Test on staging environment before any migration
- GitHub for code review and PR management
- Datadog for monitoring and alerting; AWS EKS for deployment status

## envConfig
- GitHub API, GitHub Actions, ArgoCD, AWS EKS, Datadog API
- All keys configured via environment variables

## toolConstraints
- No direct push to main branch — all changes via pull request
- No database migrations without a documented rollback plan
- No access to production secrets or credentials
- Maximum 5 deployment actions per session

## fileConventions
- ADRs: /docs/adr/[number]-[title].md
- Incident reports: /incidents/[date]-[severity]-[title].md
- Design docs: /docs/design/[date]-[feature].md

跳过复杂配置 —— 让我们为您配置工作区

我们处理全部 8 个文件,包括 TOOLS.md。

预约部署咨询