session_status
Get current session status (project loaded, modified, undo/redo levels).
This record as markdown: /tools/mcp-anything/session-status.md
What session_status does on Mcp Anything
AI agents call session_status to retrieve information from Mcp Anything without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why session_status is rated Low
This tool retrieves immutable status information about the current session state. It has no side effects, does not modify data, does not execute operations, and does not affect system state. It is purely informational, consistent with the Read category definition of tools that retrieve or query data without side effects.
From the tool's definition Tool name 'session_status' and description 'Get current session status' indicate a retrieval operation that queries state (project loaded, modified, undo/redo levels) without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs session_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For session_status, this is the rule to start with:
session_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every session_status call is checked against it from then on.
Questions about session_status
Get current session status (project loaded, modified, undo/redo levels). It is categorised as a Read tool in the Mcp Anything MCP Server, which means it retrieves data without modifying state.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for session_status: 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 Mcp Anything. Nothing to install.
session_status 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 session_status 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 session_status. 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.
session_status is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue