wger_muscles
List muscle groups from the wger workout database.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/wger-muscles.md
What wger_muscles does on UnClick
AI agents call wger_muscles to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wger_muscles is rated Low
The tool queries and returns a static list of muscle groups from a workout database. This is a straightforward read operation with no side effects, no code execution, no data modification, and no financial implications. The low severity reflects minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'wger_muscles' and description 'List muscle groups from the wger workout database' indicates a data retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs wger_muscles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wger_muscles, this is the rule to start with:
wger_muscles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every wger_muscles call is checked against it from then on.
Questions about wger_muscles
List muscle groups from the wger workout database. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for wger_muscles: 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 UnClick. Nothing to install.
wger_muscles 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 wger_muscles 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 wger_muscles. 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.
wger_muscles is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue