get_portco_emissions
AI agents call get_portco_emissions to retrieve information from northwood-carbon MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves portfolio company emissions data without modifying, deleting, or executing external operations. It fits the Read category (query/fetch pattern). Severity is low because exposure of historical emissions data poses minimal risk—it is typically non-sensitive business intelligence.
From the tool's definition Tool name 'get_portco_emissions' indicates data retrieval. Server description states it enables agents to 'query emissions' and 'analyze decarbonization gaps', positioning this as a read operation. Tool description is empty, limiting direct confirmation.
Attacks that exploit this kind of access
get_portco_emissions. It is categorised as a Read tool in the northwood-carbon MCP server MCP Server, which means it retrieves data without modifying state.
Register the northwood-carbon MCP server MCP server in PolicyLayer and add a rule for get_portco_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 northwood-carbon MCP server. Nothing to install.
get_portco_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 get_portco_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 get_portco_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.
get_portco_emissions is provided by the northwood-carbon MCP server MCP server (trippborstel-hub/northwood-carbon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →