Manage your Seracade account. Actions: start_audit (generate audit reports from your traffic), get_status (Call counts, audit progress, Routing Decisions in force), activate_routing (turn the routing table on), check_savings (lifetime routing value from Calls and Replays), set_budget (per-agent m...
Handles credentials or secrets (api_key)
Part of the Seracade MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use seracade to create or modify resources in Seracade. 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 seracade 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 Seracade.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
seracade:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Seracade policy for all 3 tools.
Agents calling write-class tools like seracade 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.
Manage your Seracade account. Actions: start_audit (generate audit reports from your traffic), get_status (Call counts, audit progress, Routing Decisions in force), activate_routing (turn the routing table on), check_savings (lifetime routing value from Calls and Replays), set_budget (per-agent monthly cap, the budget sits alongside Quality Gates). Recommended: set SERACADE_API_KEY env var instead of passing api_key inline.. It is categorised as a Write tool in the Seracade 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 seracade. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Seracade MCP server.
seracade 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 seracade 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 seracade. 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.
seracade is provided by the Seracade MCP server (seracade). 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.