carbon_vehicle_emissions
Estimate carbon emissions for a vehicle journey.
This record as markdown: /tools/creativelead-unclick/carbon-vehicle-emissions.md
What carbon_vehicle_emissions does on UnClick
AI agents call carbon_vehicle_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 |
|---|---|---|---|
api_key | string | — | |
distance_unit | string | — | |
distance_value | number | — | |
vehicle_model_id | string | — |
Parameters from the server's own tool schema.
Why carbon_vehicle_emissions is rated Low
The tool performs a read-only estimation task. It takes vehicle journey information and returns a calculated carbon emission value. There are no side effects, no data modification, no irreversible actions, no code execution, and no financial implications. This is analogous to a search or fetch operation that computes and returns information without changing any state.
From the tool's definition Tool description indicates 'Estimate carbon emissions for a vehicle journey' - this is a calculation/query operation that retrieves or computes data based on input parameters without modifying any data or executing external operations.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs carbon_vehicle_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_vehicle_emissions, this is the rule to start with:
carbon_vehicle_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_vehicle_emissions call is checked against it from then on.
Questions about carbon_vehicle_emissions
Estimate carbon emissions for a vehicle journey. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
carbon_vehicle_emissions accepts 4 parameters: api_key, distance_unit, distance_value, vehicle_model_id. 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_vehicle_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_vehicle_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_vehicle_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_vehicle_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_vehicle_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