fitness_get_connected_services
AI agents call fitness_get_connected_services to retrieve information from FitnessMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name pattern 'get_*' combined with 'connected_services' indicates a read-only retrieval operation. It queries the state of connected services without modifying data. The empty description reduces confidence slightly, but the naming convention is clear enough to categorize as a Read operation with low severity—retrieving connection status poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'fitness_get_connected_services' indicates a query operation to retrieve information about which fitness services are connected to the MCP server.
Attacks that exploit this kind of access
fitness_get_connected_services. It is categorised as a Read tool in the FitnessMCP MCP Server, which means it retrieves data without modifying state.
Register the Fitness MCP server in PolicyLayer and add a rule for fitness_get_connected_services: 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 FitnessMCP. Nothing to install.
fitness_get_connected_services 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 fitness_get_connected_services 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 fitness_get_connected_services. 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.
fitness_get_connected_services is provided by the Fitness MCP server (senoj100-alt/fitnessmcp). 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 →