wger.fitness.exercise_details
Get full exercise details by ID — description, primary and secondary muscles worked, required equipment (barbell/dumbbell/bodyweight/machine), and category. Use with exercise_search to build workout plans.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wger.fitness.exercise-details.md
What wger.fitness.exercise_details does on Apibase
AI agents call wger.fitness.exercise_details to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | integer | Yes | Exercise base ID from search results (e.g. 615 for Squats) |
Parameters from the server's own tool schema.
Why wger.fitness.exercise_details is rated Low
Read-only retrieval of static exercise data; no side effects possible.
From the tool's definition Get full exercise details by ID — description, muscles, equipment
Attacks that exploit this kind of access
The rule that runs wger.fitness.exercise_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wger.fitness.exercise_details, this is the rule to start with:
wger.fitness.exercise_details 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 Apibase, apply this rule, and every wger.fitness.exercise_details call is checked against it from then on.
Questions about wger.fitness.exercise_details
Get full exercise details by ID — description, primary and secondary muscles worked, required equipment (barbell/dumbbell/bodyweight/machine), and category. Use with exercise_search to build workout plans. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wger.fitness.exercise_details accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for wger.fitness.exercise_details: 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 Apibase. Nothing to install.
wger.fitness.exercise_details 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.fitness.exercise_details 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.fitness.exercise_details. 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.fitness.exercise_details is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue