Get the primary, secondary, and stabilizer muscles worked by an exercise.
AI agents call get_muscles_worked to retrieve information from MusclesWorked without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a static database to return muscle information for an exercise. It does not create, modify, delete, execute code, or trigger external operations. It is purely informational retrieval with no capability to alter system state or data.
From the tool's definition The tool retrieves information: 'Get the primary, secondary, and stabilizer muscles worked by an exercise.' The verb 'Get' and the action of retrieving muscle data for a given exercise indicate a query operation with no side effects.
Attacks that exploit this kind of access
Get the primary, secondary, and stabilizer muscles worked by an exercise. It is categorised as a Read tool in the MusclesWorked MCP Server, which means it retrieves data without modifying state.
Register the MusclesWorked MCP server in PolicyLayer and add a rule for get_muscles_worked: 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 MusclesWorked. Nothing to install.
get_muscles_worked 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_muscles_worked 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_muscles_worked. 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_muscles_worked is provided by the MusclesWorked MCP server (musclesworked-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 →