Load previously saved agent working state. Use this after a connection recovery to restore your context and continue where you left off.
AI agents call load_session_state to retrieve information from Agent MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and restores previously saved session state data. It performs a read operation with no side effects, no data modification, deletion, or external operations triggered. The purpose is to restore context after disconnection, which is a benign read operation.
From the tool's definition Tool name 'load_session_state' and description 'Load previously saved agent working state' indicate data retrieval without modification. The verb 'load' denotes reading/fetching existing state.
Documented attack patterns abuse exactly the kind of access load_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 load_session_state:
{
"version": "1",
"default": "deny",
"tools": {
"load_session_state": {}
}
}load_session_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Load previously saved agent working state. Use this after a connection recovery to restore your context and continue where you left off. It is categorised as a Read tool in the Agent MCP MCP Server, which means it retrieves data without modifying state.
Register the Agent MCP server in PolicyLayer and add a rule for load_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.
load_session_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the load_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 load_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.
load_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.