calculate_business_travel
Business travel emissions (Scope 3 Cat 6), distance method: emissions = km × passengers × factor. Air factors come in with_rf / without_rf (radiative forcing) variants. Find factors via search_factors (section "business_travel").
This record as markdown: /tools/com-greencalculus-api/calculate-business-travel.md
What calculate_business_travel does on Api
AI agents call calculate_business_travel to retrieve information from Api 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 |
|---|---|---|---|
distance | object | Yes | { "value": <number>, "unit": "km|mi" }. |
factor_key | string | Yes | Per-passenger-km travel factor key. |
passengers | number | — | Optional, defaults to 1. |
Parameters from the server's own tool schema.
Why calculate_business_travel is rated Low
Even though calculate_business_travel only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs calculate_business_travel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calculate_business_travel, this is the rule to start with:
calculate_business_travel 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 Api, apply this rule, and every calculate_business_travel call is checked against it from then on.
Questions about calculate_business_travel
Business travel emissions (Scope 3 Cat 6), distance method: emissions = km × passengers × factor. Air factors come in with_rf / without_rf (radiative forcing) variants. Find factors via search_factors (section "business_travel"). It is categorised as a Read tool in the Api MCP Server, which means it retrieves data without modifying state.
calculate_business_travel accepts 3 parameters: distance, factor_key, passengers. Required: distance, factor_key. The full parameter table on this page comes from the server's own tool schema.
Register the Api MCP server in PolicyLayer and add a rule for calculate_business_travel: 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 Api. Nothing to install.
calculate_business_travel 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_business_travel 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_business_travel. 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_business_travel is provided by the Api MCP server (https://mcp.greencalculus.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Api, and thousands of servers like it.
This server
Across the catalogue