Record the invocation of an AI Resource (Command or Skill) for telemetry. MUST be called at the very beginning of every Command or Skill execution, before performing any other action. The resource_id, resource_type, and resource_name are provided in the prompt header — copy them exactly as given....
Bulk/mass operation — affects multiple targets
Part of the Ai Agent MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use track_usage to create or modify resources in Ai Agent. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call track_usage repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ai Agent.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
track_usage:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Ai Agent policy for all 8 tools.
Agents calling write-class tools like track_usage have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Record the invocation of an AI Resource (Command or Skill) for telemetry. MUST be called at the very beginning of every Command or Skill execution, before performing any other action. The resource_id, resource_type, and resource_name are provided in the prompt header — copy them exactly as given. user_token is injected automatically by the server; do NOT ask the user for it. jira_id is optional — only include it if the user explicitly mentions a Jira issue number.. It is categorised as a Write tool in the Ai Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for track_usage. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ai Agent MCP server.
track_usage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the track_usage rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for track_usage. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
track_usage is provided by the Ai Agent MCP server (@elliotding/ai-agent-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.