// SCAN REPORT

Api

11 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 18 Aug 2026

1 can modify or destroy data

10 read-only

11 tools total

Community server · catalogue entry checked 18/08/2026 · full schemas captured for 11 of 11 tools

How to control Api ↓

TOOL MAP

What Api exposes to your agents

Read (10) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Api tools

Write · Medium resolve_factor Find the best emission-factor key(s) for a plain-language description — the hardest step is picking the right key out of ~16,000. Returns ra

1 of Api's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Api

PolicyLayer is an MCP gateway — it sits between your AI agents and Api, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "resolve_factor": {
    "limits": [
      {
        "counter": "resolve_factor_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "calculate_activity": {
    "limits": [
      {
        "counter": "calculate_activity_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Api — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON API →

Instant setup, no code required.

FULL CATALOGUE

All 11 Api tools

WRITE 1 tools

Write resolve_factor Find the best emission-factor key(s) for a plain-language description — the hardest step is picking the right

READ 10 tools

Read calculate_activity Turn activity data into greenhouse-gas emissions: emissions = activity × factor. Give an amount + unit and a f Read calculate_business_travel Business travel emissions (Scope 3 Cat 6), distance method: emissions = km × passengers × factor. Air factors Read calculate_electricity GHG Protocol Scope 2 for purchased electricity, both methods. Always returns location-based (grid-average) emi Read calculate_embodied Whole-life embodied carbon for materials, per EN 15978. Give a material key + quantity (+ optional boundary A1 Read calculate_freight Freight & logistics emissions (Scope 3 Cat 4 & 9), GLEC tonne-km method: emissions = tonnes × km × factor. Fin Read calculate_pcaf Compute PCAF Part A financed emissions for a portfolio. Returns each holding's attribution factor and financed Read calculate_spend Spend-based (EEIO) Scope 3 screening: emissions = spend × economic-intensity factor. Spend must be in the fact Read explain_absence Ask why a factor is NOT in the corpus. The reasoned counterpart to coverage: where a country reports zero rows Read lookup_factor Look up a single greenhouse-gas emission factor by its canonical key. Returns the value plus an audit envelope Read search_factors Find emission-factor keys by section, key prefix, or free text. Returns matching keys, names, and sections (va

FAQ

Questions about Api

How do I prevent bulk modifications through Api? +

The Api server has 1 write tools including resolve_factor. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Api.

How many tools does the Api MCP server expose? +

11 tools across 2 categories: Read, Write. 10 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Api? +

Register the Api MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Api tool call.

Deterministic rules across all 11 Api tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON API →

Instant setup, no code required.

11 Api tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Api's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →