AI agents call get_program_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 only queries and displays fitness program data. It retrieves information about training programs without creating, modifying, deleting, or executing any operations. The user can view their active programs or historical records, but no data is altered or side effects are triggered. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool description states 'View your current active training programs or browse your full program history' — purely retrieval operations with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
View your current active training programs or browse your full program history. 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_program_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_program_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_program_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_program_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_program_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 →