calculate_activity
Turn activity data into greenhouse-gas emissions: emissions = activity × factor. Give an amount + unit and a factor key; the unit engine converts to the factor basis (MWh→kWh, tonne→kg, gallon→litre, mile→km) and returns the emissions with the working, the GHG Protocol scope, and the source. Use ...
This record as markdown: /tools/com-greencalculus-api/calculate-activity.md
What calculate_activity does on Api
AI agents call calculate_activity 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 |
|---|---|---|---|
activity | object | Yes | { "value": <number>, "unit": "<unit e.g. kWh, MWh, litres, tonne, km>" }. |
factor_key | string | Yes | Canonical emission-factor key. |
Parameters from the server's own tool schema.
Why calculate_activity is rated Low
Even though calculate_activity 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_activity 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_activity, this is the rule to start with:
calculate_activity 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_activity call is checked against it from then on.
Questions about calculate_activity
Turn activity data into greenhouse-gas emissions: emissions = activity × factor. Give an amount + unit and a factor key; the unit engine converts to the factor basis (MWh→kWh, tonne→kg, gallon→litre, mile→km) and returns the emissions with the working, the GHG Protocol scope, and the source. Use search_factors / lookup_factor to find the factor key. It is categorised as a Read tool in the Api MCP Server, which means it retrieves data without modifying state.
calculate_activity accepts 2 parameters: activity, factor_key. Required: activity, 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_activity: 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_activity 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_activity 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_activity. 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_activity 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