Invoke an action on a specific provider. WRITE tool: creates leads/bookings/contacts/projects/activities/tickets on the underlying SaaS tenant. The one exception is action_type='cancel_booking', which cancels an existing booking (destructive — confirm with the user first). Validates inputs agains...
Part of the Whatcanido — MCP Server for Service Businesses server.
Free to start. No card required.
AI agents use submit_action 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 submit_action 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": {
"submit_action": {
"limits": [
{
"counter": "submit_action_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 submit_action 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.
Invoke an action on a specific provider. WRITE tool: creates leads/bookings/contacts/projects/activities/tickets on the underlying SaaS tenant. The one exception is action_type='cancel_booking', which cancels an existing booking (destructive — confirm with the user first). Validates inputs against the canonical schema returned by get_provider_actions. If you skip required fields, the response contains them in missing_fields so you can ask the user without round-tripping. Returns a request_id you can later pass to get_action_status. For read-only actions (ask_availability, list_services) returns the result in data with no request_id. Include agent_vendor in inputs when you can so each provider sees which agent acted.. 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 submit_action: 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.
submit_action 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 submit_action 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 submit_action. 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.
submit_action 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.