Search Garmin Connect IQ API documentation for modules, classes, or functions
AI agents call search_garmin_docs to retrieve information from Garmin Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves documentation content. It has no side effects, creates no data, executes no code, and cannot modify or delete information. It is purely informational retrieval, matching the Read category. Low severity because misuse only affects information access, not system state or resources.
From the tool's definition Tool is described as 'Search Garmin Connect IQ API documentation' with sibling tools including 'get_api_examples', 'get_class_details', 'get_module_details', 'get_programming_guide', 'list_modules', 'search_device_reference', and 'search_faq' — all…
Documented attack patterns abuse exactly the kind of access search_garmin_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin Documentation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_garmin_docs:
{
"version": "1",
"default": "deny",
"tools": {
"search_garmin_docs": {}
}
}search_garmin_docs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search Garmin Connect IQ API documentation for modules, classes, or functions. It is categorised as a Read tool in the Garmin Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Garmin Documentation MCP Server MCP server in PolicyLayer and add a rule for search_garmin_docs: 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 Garmin Documentation MCP Server. Nothing to install.
search_garmin_docs 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 search_garmin_docs 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 search_garmin_docs. 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.
search_garmin_docs is provided by the Garmin Documentation MCP Server MCP server (ztuskes/garmin-documentation-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Garmin Documentation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Garmin Documentation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.