Given a user intent, return a typed plan: an ordered list of capability calls that together accomplish the goal, with the highest-reputation provider per step. The plan respects the capability registry's prerequisite graph — for example a plan that includes booking.create_booking automatically pr...
Part of the Whatcanido — MCP Server for Service Businesses server.
Free to start. No card required.
AI agents use plan_capabilities to create or modify resources in Whatcanido — MCP Server for Service Businesses. 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 plan_capabilities repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Whatcanido — MCP Server for Service Businesses.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"plan_capabilities": {
"limits": [
{
"counter": "plan_capabilities_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Whatcanido — MCP Server for Service Businesses policy for all 10 tools.
These attack patterns abuse exactly the kind of access plan_capabilities gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Given a user intent, return a typed plan: an ordered list of capability calls that together accomplish the goal, with the highest-reputation provider per step. The plan respects the capability registry's prerequisite graph — for example a plan that includes booking.create_booking automatically prepends booking.check_availability. Use this when the user's request spans more than one verb (e.g. 'find me an open yoga slot tomorrow morning and book it'). Each step exposes capability_id, provider, conformance, p50 latency, cost, and a prerequisite_for array. The agent then iterates through the plan calling invoke_capability per step.. It is categorised as a Write tool in the Whatcanido — MCP Server for Service Businesses MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Whatcanido — MCP Server for Service Businesses MCP server in PolicyLayer and add a rule for plan_capabilities: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Whatcanido — MCP Server for Service Businesses. Nothing to install.
plan_capabilities 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 plan_capabilities rule in your PolicyLayer 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 PolicyLayer policy for plan_capabilities. 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.
plan_capabilities is provided by the Whatcanido — MCP Server for Service Businesses MCP server (https://whatcanido.dev/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Whatcanido — MCP Server for Service Businesses tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.