AI agents use log_workout to create or update resources in Pelaris — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pelaris environment.
This tool creates a new workout log entry in the system. It writes data (exercises, RPE, subjective feelings) to persistent storage. It is reversible — the sibling tools delete_session/delete_sessions suggest records can be removed. No code execution, financial transactions, or irreversible destruction is involved.
From the tool's definition "Record a completed workout with exercises, RPE, and how you felt. Duplicate entries are automatically prevented."
Attacks that exploit this kind of access
Record a completed workout with exercises, RPE, and how you felt. Duplicate entries are automatically prevented. It is categorised as a Write tool in the Pelaris MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pelaris MCP server in PolicyLayer and add a rule for log_workout: 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.
log_workout is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the log_workout 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 log_workout. 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.
log_workout 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 →