[Deprecated: Use aiobs_get_session] Get detailed information about a specific AI agent session.
AI agents call get_session to retrieve information from Shepherd MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves session data from observability providers for debugging and analysis purposes. It has no side effects—it does not create, modify, delete, or execute operations. The action is purely informational retrieval, making it a Read category risk with low severity.
From the tool's definition Tool name 'get_session' and description 'Get detailed information about a specific AI agent session' indicate data retrieval without modification. The deprecation notice directs users to 'aiobs_get_session', which follows the same read pattern.
Attacks that exploit this kind of access
[Deprecated: Use aiobs_get_session] Get detailed information about a specific AI agent session. It is categorised as a Read tool in the Shepherd MCP MCP Server, which means it retrieves data without modifying state.
Register the Shepherd MCP server in PolicyLayer and add a rule for get_session: 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 Shepherd MCP. Nothing to install.
get_session 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 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. 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 is provided by the Shepherd MCP server (neuralis-in/shepherd-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 →