Returns a real-time diagnostic snapshot of the current dev environment. Includes health diagnosis, running services, recent errors, git state, and environment info. Call this first to orient yourself in the user
AI agents call get_session_snapshot to retrieve information from Devpulse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the state of a local development environment without causing any side effects, modifications, or state changes. It is purely informational, making it a Read category tool. Severity is low because the information exposed is limited to the developer's own local environment diagnostics with no capability to alter systems, execute arbitrary commands, or access sensitive external resources.
From the tool's definition Tool 'get_session_snapshot' returns diagnostic information about the dev environment (health diagnosis, running services, recent errors, git state, environment info) with no indication of modification, deletion, or code execution capabilities.
Attacks that exploit this kind of access
Returns a real-time diagnostic snapshot of the current dev environment. Includes health diagnosis, running services, recent errors, git state, and environment info. Call this first to orient yourself in the user. It is categorised as a Read tool in the Devpulse MCP Server, which means it retrieves data without modifying state.
Register the Devpulse MCP server in PolicyLayer and add a rule for get_session_snapshot: 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 Devpulse. Nothing to install.
get_session_snapshot 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_snapshot 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_snapshot. 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_snapshot is provided by the Devpulse MCP server (tao-izm/devpulse-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 →