Return the most recent HabitTracker daily body-weight metric.
AI agents call get_latest_body_weight to retrieve information from Poke HabitTracker MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical health data without modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves a single metric value. The blast radius is minimal—misuse would only expose personal health information already stored in the user's HabitTracker, with no capability to modify or delete data.
From the tool's definition Tool name 'get_latest_body_weight' and description 'Return the most recent HabitTracker daily body-weight metric' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Return the most recent HabitTracker daily body-weight metric. It is categorised as a Read tool in the Poke HabitTracker MCP MCP Server, which means it retrieves data without modifying state.
Register the Poke HabitTracker MCP server in PolicyLayer and add a rule for get_latest_body_weight: 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 Poke HabitTracker MCP. Nothing to install.
get_latest_body_weight 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 get_latest_body_weight 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 get_latest_body_weight. 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.
get_latest_body_weight is provided by the Poke HabitTracker MCP server (smoothiekanoble/poke-mcp). 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 →