log_body_metrics
AI agents use log_body_metrics to create or update resources in MCP Logger — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Logger environment.
The tool name 'log_body_metrics' strongly implies creating or recording body metric data (e.g., weight, body fat) into the local SQLite database. This is a Write operation as it adds new records. Severity is medium since misuse could corrupt personal health tracking data. Confidence is reduced due to the empty description, but the name and server context are fairly clear.
From the tool's definition Tool name 'log_body_metrics' combined with server description mentioning 'logging... body metrics through a local SQLite database'
Attacks that exploit this kind of access
log_body_metrics. It is categorised as a Write tool in the MCP Logger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Logger MCP server in PolicyLayer and add a rule for log_body_metrics: 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 MCP Logger. Nothing to install.
log_body_metrics is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the log_body_metrics 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 log_body_metrics. 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.
log_body_metrics is provided by the MCP Logger MCP server (johnzolton/mcp-logger). 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 →