carbon_roadmap
Roadmap carbone — Gapup agent-payable C-suite expertise (SUSTAINABILITY). Returns a structured, audited deliverable. Reference case: Cas démo — Roadmap carbone. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/carbon-roadmap.md
What carbon_roadmap does on Gapup Mcp
AI agents call carbon_roadmap as a supporting operation in Gapup Mcp workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
focus | string | — | |
company | object | Yes | |
perimeter | object | Yes | |
scope1Sources | array | — | |
scope2Sources | array | Yes | |
reductionTargets | object | — | |
scope3Activities | array | — |
Parameters from the server's own tool schema.
Why carbon_roadmap is rated Low
This tool generates a carbon roadmap report/deliverable for sustainability purposes. It reads/queries and returns a structured document — no money movement, no destructive action, no code execution, and no direct data write is described. It fits closest to Read (retrieval of structured analysis), though the 'agent-payable' x402 per-call billing model is notable.
From the tool's definition 'Roadmap carbone — Gapup agent-payable C-suite expertise (SUSTAINABILITY). Returns a structured, audited deliverable.'
Risk signalsHigh parameter count (32 properties)
Attacks that exploit this kind of access
The rule that runs carbon_roadmap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For carbon_roadmap, this is the rule to start with:
carbon_roadmap gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every carbon_roadmap call is checked against it from then on.
Questions about carbon_roadmap
Roadmap carbone — Gapup agent-payable C-suite expertise (SUSTAINABILITY). Returns a structured, audited deliverable. Reference case: Cas démo — Roadmap carbone. Inputs are validated server-side — send the documented case fields. It is categorised as a Other tool in the Gapup Mcp MCP Server, which means it performs auxiliary operations.
carbon_roadmap accepts 8 parameters: async, focus, company, perimeter, scope1Sources, scope2Sources, reductionTargets, scope3Activities. Required: company, perimeter, scope2Sources. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for carbon_roadmap: 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 Gapup Mcp. Nothing to install.
carbon_roadmap is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the carbon_roadmap 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 carbon_roadmap. 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.
carbon_roadmap is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue