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

Agent View of the PolicyLayer registry record for `calculate_spend`. HTML page: https://policylayer.com/tools/com-greencalculus-api/calculate-spend

## Facts

- Tool: `calculate_spend`
- Server: Api (`https://mcp.greencalculus.com`) — https://policylayer.com/tools/com-greencalculus-api.md
- Homepage: https://github.com/https://mcp.greencalculus.com
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Allowed

## Parameters

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

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "calculate_spend",
    "arguments": {
      "spend": {},
      "factor_key": "<factor_key>"
    }
  }
}
```

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

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Api:

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

## Other tools on Api (10)

- `calculate_activity` — Read — https://policylayer.com/tools/com-greencalculus-api/calculate-activity.md
- `calculate_business_travel` — Read — https://policylayer.com/tools/com-greencalculus-api/calculate-business-travel.md
- `calculate_electricity` — Read — https://policylayer.com/tools/com-greencalculus-api/calculate-electricity.md
- `calculate_embodied` — Read — https://policylayer.com/tools/com-greencalculus-api/calculate-embodied.md
- `calculate_freight` — Read — https://policylayer.com/tools/com-greencalculus-api/calculate-freight.md
- `calculate_pcaf` — Read — https://policylayer.com/tools/com-greencalculus-api/calculate-pcaf.md
- `explain_absence` — Read — https://policylayer.com/tools/com-greencalculus-api/explain-absence.md
- `lookup_factor` — Read — https://policylayer.com/tools/com-greencalculus-api/lookup-factor.md
- `search_factors` — Read — https://policylayer.com/tools/com-greencalculus-api/search-factors.md
- `resolve_factor` — Write — https://policylayer.com/tools/com-greencalculus-api/resolve-factor.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-greencalculus-api · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-greencalculus-api