carbon_flight_emissions
Estimate carbon emissions for a flight.
This record as markdown: /tools/creativelead-unclick/carbon-flight-emissions.md
What carbon_flight_emissions does on UnClick
AI agents call carbon_flight_emissions to retrieve information from UnClick 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 |
|---|---|---|---|
legs | array | — | Array of flight legs with departure_airport and destination_airport |
api_key | string | — | |
passengers | number | — |
Parameters from the server's own tool schema.
Why carbon_flight_emissions is rated Low
This tool queries or computes flight carbon emission estimates based on input parameters. It is purely informational with no side effects, no code execution triggered on external systems, no data modification, no deletions, and no financial transactions. It fits cleanly into the Read category as a retrieval/calculation tool.
From the tool's definition Tool name and description indicate it 'Estimate carbon emissions for a flight' — a read-only operation that retrieves or calculates data without modifying, executing external operations, or causing financial/destructive effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs carbon_flight_emissions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For carbon_flight_emissions, this is the rule to start with:
carbon_flight_emissions 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 UnClick, apply this rule, and every carbon_flight_emissions call is checked against it from then on.
Questions about carbon_flight_emissions
Estimate carbon emissions for a flight. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
carbon_flight_emissions accepts 3 parameters: legs, api_key, passengers. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for carbon_flight_emissions: 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 UnClick. Nothing to install.
carbon_flight_emissions 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 carbon_flight_emissions 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_flight_emissions. 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_flight_emissions is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue