AI agents call getSteps to retrieve information from FitBit MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves step count data from Fitbit without modifying, executing operations, or causing financial impact. It is a straightforward data query operation consistent with the 'Read' category. Confidence is high despite the empty description because the pattern of sibling tools and server purpose strongly indicate data retrieval only.
From the tool's definition Tool name 'getSteps' combined with sibling tools like 'getActiveZoneMinutes', 'getActivities', 'getHeartRate' which are all data retrieval operations from Fitbit's health API.
Documented attack patterns abuse exactly the kind of access getSteps gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FitBit MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for getSteps:
{
"version": "1",
"default": "deny",
"tools": {
"getSteps": {}
}
}getSteps 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.
getSteps. It is categorised as a Read tool in the FitBit MCP MCP Server, which means it retrieves data without modifying state.
Register the FitBit MCP server in PolicyLayer and add a rule for getSteps: 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 FitBit MCP. Nothing to install.
getSteps 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 getSteps 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 getSteps. 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.
getSteps is provided by the FitBit MCP server (nitayrabi/fitbit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FitBit MCP, 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.
16 FitBit MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.