AI agents call get_generation_status to retrieve information from Pelaris without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about an asynchronous job—a pure read operation with no side effects. It only returns metadata about progress and session counts, making it a Read category tool with low severity since misuse would only expose information, not cause harm or enable unintended actions.
From the tool's definition Tool name 'get_generation_status' and description 'Check the status of a training plan generation job. Returns progress through pipeline stages and session count when complete.' indicate a query operation that retrieves status information without modifying,…
Attacks that exploit this kind of access
Check the status of a training plan generation job. Returns progress through pipeline stages and session count when complete. It is categorised as a Read tool in the Pelaris MCP Server, which means it retrieves data without modifying state.
Register the Pelaris MCP server in PolicyLayer and add a rule for get_generation_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 Pelaris. Nothing to install.
get_generation_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_generation_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_generation_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_generation_status is provided by the Pelaris MCP server (thedonk/pelaris-mcp-server). 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 →