search_factors
Find emission-factor keys by section, key prefix, or free text. Returns matching keys, names, and sections (values are redacted here — call lookup_factor for the value).
This record as markdown: /tools/com-greencalculus-api/search-factors.md
What search_factors does on Api
AI agents call search_factors 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 |
|---|---|---|---|
limit | number | — | Max results (default 20). |
query | string | — | Free-text search over factor names/keys. |
section | string | — | Restrict to a section, e.g. "grid", "fuels", "freight". |
key_prefix | string | — | Restrict to keys starting with this prefix. |
Parameters from the server's own tool schema.
Why search_factors is rated Low
Even though search_factors 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 search_factors 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 search_factors, this is the rule to start with:
search_factors 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 search_factors call is checked against it from then on.
Questions about search_factors
Find emission-factor keys by section, key prefix, or free text. Returns matching keys, names, and sections (values are redacted here — call lookup_factor for the value). It is categorised as a Read tool in the Api MCP Server, which means it retrieves data without modifying state.
search_factors accepts 4 parameters: limit, query, section, key_prefix. 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 search_factors: 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.
search_factors 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 search_factors 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 search_factors. 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.
search_factors 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