Load a specific archived chat session by its ID
AI agents call loadSession to retrieve information from Mup without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves historical chat session data. It does not create, modify, delete, or execute any external operations. The action is non-destructive and has minimal security impact since it only accesses existing archived data. The blast radius of misuse is limited to unauthorized information disclosure of previously stored chat sessions.
From the tool's definition "Load a specific archived chat session by its ID" - the tool retrieves/queries an existing archived session without modifying or deleting it.
Documented attack patterns abuse exactly the kind of access loadSession gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mup, and nothing reaches the server without passing your rules. This is the rule we recommend for loadSession:
{
"version": "1",
"default": "deny",
"tools": {
"loadSession": {}
}
}loadSession 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 a specific archived chat session by its ID. It is categorised as a Read tool in the Mup MCP Server, which means it retrieves data without modifying state.
Register the Mup MCP server in PolicyLayer and add a rule for loadSession: 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 Mup. Nothing to install.
loadSession 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 loadSession 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 loadSession. 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.
loadSession is provided by the Mup MCP server (mup-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mup, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Mup tools catalogued and risk-classified — across an index of 43,000+ MCP servers.