Calculate Scope 3.1 emissions from procurement spending using economic input-output life cycle assessment methods.
AI agents call procurement-emission to retrieve information from Climatiq MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a calculation/estimation of carbon emissions based on procurement data. It reads inputs, runs a computation against the Climatiq API, and returns results. There are no side effects such as writing, deleting, executing code, or moving money. The financial data (spending) is used as an input parameter for the emissions calculation, not to execute any financial transaction.
From the tool's definition Calculate Scope 3.1 emissions from procurement spending using economic input-output life cycle assessment methods
Documented attack patterns abuse exactly the kind of access procurement-emission gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Climatiq MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for procurement-emission:
{
"version": "1",
"default": "deny",
"tools": {
"procurement-emission": {}
}
}procurement-emission is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Calculate Scope 3.1 emissions from procurement spending using economic input-output life cycle assessment methods. It is categorised as a Read tool in the Climatiq MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Climatiq MCP Server MCP server in PolicyLayer and add a rule for procurement-emission: 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 Climatiq MCP Server. Nothing to install.
procurement-emission 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 procurement-emission 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 procurement-emission. 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.
procurement-emission is provided by the Climatiq MCP Server MCP server (jagan-shanmugam/climatiq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Climatiq MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Climatiq MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.