Calculate BMI from weight and height
AI agents call calculate_bmi to retrieve information from Simple MCP Server with Streamable HTTP Example without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
BMI calculation is a pure mathematical function that takes weight and height as inputs and returns a computed value. It reads/processes input data without modifying any external state, storing data, or triggering any external operations. Severity is low as misuse has negligible blast radius.
From the tool's definition "Calculate BMI from weight and height" — performs a mathematical computation on provided inputs with no side effects
Attacks that exploit this kind of access
Calculate BMI from weight and height. It is categorised as a Read tool in the Simple MCP Server with Streamable HTTP Example MCP Server, which means it retrieves data without modifying state.
Register the Simple MCP Server with Streamable HTTP Example MCP server in PolicyLayer and add a rule for calculate_bmi: 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 Simple MCP Server with Streamable HTTP Example. Nothing to install.
calculate_bmi 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 calculate_bmi 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 calculate_bmi. 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.
calculate_bmi is provided by the Simple MCP Server with Streamable HTTP Example MCP server (jonigl/mcp-server-with-streamable-http-example). 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 →