Execute any EcoSemantic LCA tool by name. Use discover_available_lca_tools() first to find available tools and their required parameters. Session defaults (set via set_lca_session_defaults) are applied automatically. Parameters: tool_name: Name of the tool to execute (e.g., 'search_activiti...
Single-target operation
Part of the Carbonfootprint MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke execute_lca_tool to trigger processes or run actions in Carbonfootprint. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
execute_lca_tool can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
execute_lca_tool:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Carbonfootprint policy for all 5 tools.
Agents calling execute-class tools like execute_lca_tool have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
execute_lca_tool is one of the high-risk operations in Carbonfootprint. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Execute any EcoSemantic LCA tool by name. Use discover_available_lca_tools() first to find available tools and their required parameters. Session defaults (set via set_lca_session_defaults) are applied automatically. Parameters: tool_name: Name of the tool to execute (e.g., 'search_activities') params: Dictionary of parameters for the tool Example: execute_lca_tool(tool_name="search_activities", params={"q": "electricity", "database": "ecoinvent-3.9.1-cutoff"}). It is categorised as a Execute tool in the Carbonfootprint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for execute_lca_tool. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Carbonfootprint MCP server.
execute_lca_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_lca_tool rule in your Intercept 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 Intercept policy for execute_lca_tool. 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.
execute_lca_tool is provided by the Carbonfootprint MCP server (ecosemantic/carbonfootprint). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept