Save agent working state for session recovery. Use this to preserve important context, task progress, or conversation state that should survive connection drops.
AI agents use save_session_state to create or update resources in Agent MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent MCP environment.
This tool creates or modifies session state records for recovery purposes. It does not retrieve data (Read), execute arbitrary code (Execute), irreversibly delete data (Destructive), or move money (Financial). The severity is low because saving session state is a normal operational function with minimal blast radius — even if misused, the agent would only overwrite recoverable session data.
From the tool's definition The tool is described as 'Save agent working state' — the key verb 'Save' indicates data creation/modification. The description explicitly states it 'preserve[s] important context, task progress, or conversation state', which are reversible write operations.
Documented attack patterns abuse exactly the kind of access save_session_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for save_session_state:
{
"version": "1",
"default": "deny",
"tools": {
"save_session_state": {
"limits": [
{
"counter": "save_session_state_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_session_state stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save agent working state for session recovery. Use this to preserve important context, task progress, or conversation state that should survive connection drops. It is categorised as a Write tool in the Agent MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent MCP server in PolicyLayer and add a rule for save_session_state: 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 Agent MCP. Nothing to install.
save_session_state 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 save_session_state 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 save_session_state. 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.
save_session_state is provided by the Agent MCP server (rinadelph/agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Agent MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Agent MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.