pet_calorie
Pet Daily Calorie Calculator — Daily calorie needs for a dog or cat (RER/MER from body weight + life stage) plus cups-per-day at common food energy densities.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/pet-calorie.md
What pet_calorie does on Gateway
AI agents call pet_calorie to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
species | string | — | 'dog' or 'cat' (default 'dog') |
weight_kg | number | Yes | Body weight in kilograms |
life_stage | string | — | neutered_adult | intact_adult | weight_loss | weight_gain | active | puppy_kitten | senior (default neutered_adult) |
Parameters from the server's own tool schema.
Why pet_calorie is rated Low
This is a straightforward calculator that retrieves and computes pet nutrition information based on input parameters (body weight, life stage, food energy density). It produces informational output only, with no side effects on any system state, data persistence, external services, or financial transactions. Classification as Read is appropriate for read-only computational tools.
From the tool's definition Tool name 'pet_calorie' and description indicate it 'calculates daily calorie needs' and 'cups-per-day' — pure computational output with no data modification, deletion, execution of external code, or financial operations.
Attacks that exploit this kind of access
The rule that runs pet_calorie safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pet_calorie, this is the rule to start with:
pet_calorie is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every pet_calorie call is checked against it from then on.
Questions about pet_calorie
Pet Daily Calorie Calculator — Daily calorie needs for a dog or cat (RER/MER from body weight + life stage) plus cups-per-day at common food energy densities. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
pet_calorie accepts 3 parameters: species, weight_kg, life_stage. Required: weight_kg. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for pet_calorie: 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 Gateway. Nothing to install.
pet_calorie 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 pet_calorie 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 pet_calorie. 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.
pet_calorie is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue