calculate_spend

Spend-based (EEIO) Scope 3 screening: emissions = spend × economic-intensity factor. Spend must be in the factor's own currency/year (no FX). Find sector factors via search_factors (section "spend_based"), e.g. spend_based.us.naics6.541511.custom_computer_programming.

SERVERApi SOURCEhttps://mcp.greencalculus.com

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-greencalculus-api/calculate-spend.md

WHAT IT DOES

What calculate_spend does on Api

AI agents call calculate_spend 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
`spend`	object	Yes	{ "value": <number>, "currency": "USD\|GBP\|EUR\|SGD" }.
`factor_key`	string	Yes	Spend-based (EEIO) sector factor key.

Parameters from the server's own tool schema.

RISK

Why calculate_spend is rated Low

Even though calculate_spend 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

RECOMMENDED RULE

The rule that runs calculate_spend 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_spend, this is the rule to start with:

calculate_spend Allowed

calculate_spend is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calculate_spend": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Api, apply this rule, and every calculate_spend call is checked against it from then on.

FAQ

Questions about calculate_spend

What does the calculate_spend tool do? +

What parameters does calculate_spend accept? +

calculate_spend accepts 2 parameters: spend, factor_key. Required: spend, factor_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on calculate_spend? +

Register the Api MCP server in PolicyLayer and add a rule for calculate_spend: 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.

What risk level is calculate_spend? +

calculate_spend is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit calculate_spend? +

Yes. Add a rate_limit block to the calculate_spend 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.

How do I block calculate_spend completely? +

Set action: deny in the PolicyLayer policy for calculate_spend. 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.

What MCP server provides calculate_spend? +

calculate_spend 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.

KEEP EXPLORING

More on Api, and thousands of servers like it.

This server

All 11 Api tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →