my_sessions
AI agents call my_sessions to retrieve information from Astria-Index without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and context of an AI memory system with sibling tools like 'list_memories' and 'recall', 'my_sessions' most likely retrieves a list of the user's sessions. Empty description lowers confidence significantly.
From the tool's definition Tool name 'my_sessions' suggests listing or retrieving session data; description is empty and uninformative.
Attacks that exploit this kind of access
my_sessions. It is categorised as a Read tool in the Astria-Index MCP Server, which means it retrieves data without modifying state.
Register the Astria-Index MCP server in PolicyLayer and add a rule for my_sessions: 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 Astria-Index. Nothing to install.
my_sessions 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 my_sessions 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 my_sessions. 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.
my_sessions is provided by the Astria-Index MCP server (pl-odin/astria-plugin). 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 →