resolve_factor

SERVERApi SOURCEhttps://mcp.greencalculus.com

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-greencalculus-api/resolve-factor.md

WHAT IT DOES

What resolve_factor does on Api

AI agents use resolve_factor to create or update resources in Api, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Api environment.

Parameter	Type	Required	Description
`limit`	number	—	Optional, default 5.
`section`	string	—	Optional section filter, e.g. "fuels", "grid", "freight".
`description`	string	Yes	What you need a factor for, INCLUDING the country if it matters, e.g. "UK grid electricity", "diesel per litre France", "hotel stay Japan". Geography is parsed

Parameters from the server's own tool schema.

RISK

Why resolve_factor is rated Medium

An AI agent can call resolve_factor faster than any human can review: one bad instruction and it creates or modifies resources in Api by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

resolve_factor Rate-limited

resolve_factor stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_factor": {
      "limits": [
        {
          "counter": "resolve_factor_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about resolve_factor

What does the resolve_factor tool do? +

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 ranked candidates; feed the chosen key to a calculate_* tool or lookup_factor. Prefer this over guessing a key. PUT THE COUNTRY IN THE DESCRIPTION. Geography is read from the description text itself, not from a separate field — "diesel per litre" and "diesel per litre France" resolve differently, and omitting the country will quietly return a factor from somewhere else marked "geo_match":"proxy". ACT ON THE LABEL. Every candidate carries label: "accept" or "review", plus "why". "accept" means confidence >= 0.85 and no demotion applied — right about nine times in ten. "review" means the answer may be usable but something is off (low confidence, only one term matched, a proxy country, or a gate demoted it); confirm it before adopting the number rather than using it silently. Roughly half of CORRECT answers are also flagged "review" — that is the intended trade, so treat "review" as "check this", not "discard this". A MISS MAY EXPLAIN ITSELF. When nothing matches, or the only matches are from the wrong country, the response may carry an "absence" object saying WHY. classification "structural" means no publisher issues this anywhere — STOP, do not retry with reworded queries and do not substitute a different country without saying so. "not_yet_sourced" means a publisher exists and we have not ingested it (the publisher is named). "refused" means we found the data and declined it, with the reason. "coupled" means this reads empty only because a related family is empty. Use explain_absence to ask the same question directly. It is categorised as a Write tool in the Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does resolve_factor accept? +

resolve_factor accepts 3 parameters: limit, section, description. Required: description. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resolve_factor? +

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

resolve_factor is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_factor? +

Yes. Add a rate_limit block to the resolve_factor 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 resolve_factor completely? +

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

resolve_factor 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

resolve_projects on ACE-MCP →resolve_circuit on 0gzk → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →