Low Risk

get_execution_trace

Run validation and return the detailed execution trace. Shows the exact sequence of validation nodes that ran, whether each was deterministic, and the runtime of each node. Use for debugging, compliance audits, or understanding exactly what the platform checked. Different from validate: validate ...

Risk signalsHandles credentials or secrets (api_key) · Bulk/mass operation — affects multiple targets

Part of the Governance Platform server.

get_execution_trace is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE GOVERNANCE PLATFORM →

Free to start. No card required.

AI agents call get_execution_trace to retrieve information from Governance Platform without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_execution_trace only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_execution_trace": {}
  }
}

See the full Governance Platform policy for all 31 tools.

Get this rule live on your own Governance Platform server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GOVERNANCE PLATFORM →

View all 31 tools →

These attack patterns abuse exactly the kind of access get_execution_trace gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_execution_trace only ever does what you allow.

SECURE GOVERNANCE PLATFORM →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_execution_trace tool do? +

Run validation and return the detailed execution trace. Shows the exact sequence of validation nodes that ran, whether each was deterministic, and the runtime of each node. Use for debugging, compliance audits, or understanding exactly what the platform checked. Different from validate: validate returns the verdict (PASS / FAIL / REVIEW) and the state vector summary. get_execution_trace returns everything validate does PLUS the per-node trace records. Use validate for normal operation; use get_execution_trace when you need to see inside the pipeline (debugging, audit prep, latency analysis). The trace is the same whether validation passes or fails — every node that ran is recorded with its inputs, outputs, and timing. Args: api_key: GeodesicAI API key (starts with gai_) structured_data: The data to trace validation for blueprint: Blueprint to validate against. Caller must own the Blueprint. Returns: status: "PASS" / "FAIL" / "REVIEW" / "ERROR" determinism_hash: cryptographic hash of inputs + rules trace: ordered list of node records, each with: node_name, node_type, deterministic (bool), runtime_ms, inputs, outputs node_count: number of nodes in the trace deterministic_count: how many nodes were deterministic state_vector: same state_vector validate returns. It is categorised as a Read tool in the Governance Platform MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_execution_trace? +

Register the Governance Platform MCP server in PolicyLayer and add a rule for get_execution_trace: 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 Governance Platform. Nothing to install.

What risk level is get_execution_trace? +

get_execution_trace is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_execution_trace? +

Yes. Add a rate_limit block to the get_execution_trace 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.

How do I block get_execution_trace completely? +

Set action: deny in the PolicyLayer policy for get_execution_trace. 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.

What MCP server provides get_execution_trace? +

get_execution_trace is provided by the Governance Platform MCP server (https://app.geodesiclabs.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Governance Platform tool call.

Deterministic rules across all 31 Governance Platform tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.