lookup_factor
Look up a single greenhouse-gas emission factor by its canonical key. Returns the value plus an audit envelope: provenance (publisher, exact source cell, retrieval date, LICENCE and whether it may be redistributed, with the attribution the licence requires) and verification (whether the per-gas c...
This record as markdown: /tools/com-greencalculus-api/lookup-factor.md
What lookup_factor does on Api
AI agents call lookup_factor 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 |
|---|---|---|---|
key | string | Yes | Canonical factor key, e.g. "grid.deu.electricity.location_based". |
Parameters from the server's own tool schema.
Why lookup_factor is rated Low
Even though lookup_factor 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 lookup_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 lookup_factor, this is the rule to start with:
lookup_factor 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 lookup_factor call is checked against it from then on.
Questions about lookup_factor
Look up a single greenhouse-gas emission factor by its canonical key. Returns the value plus an audit envelope: provenance (publisher, exact source cell, retrieval date, LICENCE and whether it may be redistributed, with the attribution the licence requires) and verification (whether the per-gas components sum to the headline, the GWP set, and the source note stating what the publisher did NOT provide). If the key does not exist you get candidate keys back rather than a dead end. Use search_factors first if you do not know the key. It is categorised as a Read tool in the Api MCP Server, which means it retrieves data without modifying state.
lookup_factor accepts 1 parameter: key. Required: 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 lookup_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.
lookup_factor 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 lookup_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.
Set action: deny in the PolicyLayer policy for lookup_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.
lookup_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.
More on Api, and thousands of servers like it.
This server
Across the catalogue