tool_session_status
Inspect one active tool session by id without listing other clients
This record as markdown: /tools/heznpc-airmcp/tool-session-status.md
What tool_session_status does on AirMCP
AI agents call tool_session_status to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why tool_session_status is rated Low
This tool retrieves and displays information about an active session identified by id. It is purely informational with no side effects, no data modification, no code execution, and no irreversible actions. The blast radius of misuse is minimal—an agent could observe session details but cannot alter, delete, or execute operations through this tool alone. This is a straightforward Read classification.
From the tool's definition The tool 'Inspect one active tool session by id without listing other clients' performs a read-only query operation.
Attacks that exploit this kind of access
The rule that runs tool_session_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tool_session_status, this is the rule to start with:
tool_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 AirMCP, apply this rule, and every tool_session_status call is checked against it from then on.
Questions about tool_session_status
Inspect one active tool session by id without listing other clients. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for tool_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 AirMCP. Nothing to install.
tool_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 tool_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 tool_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.
tool_session_status is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue