Returns the current debug session status. Call this FIRST before starting a new session. WHEN TO USE: - Before start_debug_session: Check if a session is already active - During debugging: See current location and available actions - After errors: Diagnose session state RETURNS: - active: Whether...
AI agents call get_session_status to retrieve information from Smart Xdebug without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure query/inspection tool that retrieves read-only information about an active XDebug session. It has no capability to modify state, execute code, delete data, or move money.
From the tool's definition Tool name 'get_session_status' and description indicate it 'Returns the current debug session status' with no modification or execution capabilities.
Attacks that exploit this kind of access
Returns the current debug session status. Call this FIRST before starting a new session. WHEN TO USE: - Before start_debug_session: Check if a session is already active - During debugging: See current location and available actions - After errors: Diagnose session state RETURNS: - active: Whether a session exists - status: Current state (see below) - location: Current file and line when paused - available_actions: Valid control_execution actions - breakpoints: List of registered breakpoints SESSION STATES: -. It is categorised as a Read tool in the Smart Xdebug MCP Server, which means it retrieves data without modifying state.
Register the Smart Xdebug MCP server in PolicyLayer and add a rule for get_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 Smart Xdebug. Nothing to install.
get_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 get_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 get_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.
get_session_status is provided by the Smart Xdebug MCP server (wallter/smart-xdebug-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →