Push actions into a session's message queue (set fields, submit computation, trigger plot, etc.)
Risk signalsAccepts freeform code/query input (actions[].expression) · High parameter count (43 properties)
Part of the Calculator server.
Free to start. No card required.
AI agents use push_session_action to create or modify resources in Calculator. 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 push_session_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 Calculator.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"push_session_action": {
"limits": [
{
"counter": "push_session_action_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Calculator policy for all 10 tools.
These attack patterns abuse exactly the kind of access push_session_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.
Push actions into a session's message queue (set fields, submit computation, trigger plot, etc.). It is categorised as a Write tool in the Calculator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Calculator MCP server in PolicyLayer and add a rule for push_session_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 Calculator. Nothing to install.
push_session_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 push_session_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 push_session_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.
push_session_action is provided by the Calculator MCP server (https://mcpcalc.com/api/v1/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 Calculator 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.