wger.fitness.exercise_search
Search 896 exercises by name — bench press, squat, deadlift, curl, etc. Returns exercise name, category (Chest/Back/Legs/Arms/Abs/Shoulders/Cardio), and ID for details lookup. Open-source fitness database (Wger, CC-BY-SA).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wger.fitness.exercise-search.md
What wger.fitness.exercise_search does on Apibase
AI agents call wger.fitness.exercise_search 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 |
|---|---|---|---|
term | string | Yes | Exercise name to search (e.g. "bench press", "squat", "deadlift", "bicep curl") |
Parameters from the server's own tool schema.
Why wger.fitness.exercise_search is rated Low
Retrieves exercise data from public fitness database with no side effects or mutations.
From the tool's definition Search exercises by name, returns exercise name, category, and ID.
Attacks that exploit this kind of access
The rule that runs wger.fitness.exercise_search 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_search, this is the rule to start with:
wger.fitness.exercise_search 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_search call is checked against it from then on.
Questions about wger.fitness.exercise_search
Search 896 exercises by name — bench press, squat, deadlift, curl, etc. Returns exercise name, category (Chest/Back/Legs/Arms/Abs/Shoulders/Cardio), and ID for details lookup. Open-source fitness database (Wger, CC-BY-SA). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wger.fitness.exercise_search accepts 1 parameter: term. Required: term. 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_search: 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_search 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_search 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_search. 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_search 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