execute_with_context | PolicyLayer

WHAT IT DOES

What execute_with_context does on Agent Passport System — Cryptographic Identity for AI Agents

AI agents invoke execute_with_context to trigger actions in Agent Passport System — Cryptographic Identity for AI Agents. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`scope`	string	Yes	Required scope for this action (must match a delegated scope)
`target`	string	Yes	Target of the action (e.g. URL, file path, resource ID)
`action_type`	string	Yes	Action type (e.g. 'api:fetch', 'data:write', 'commerce:checkout')
`estimated_spend`	number	—	Estimated spend for commerce actions

Parameters from the server's own tool schema.

THE RISK

High Risk

Why execute_with_context needs a policy

The word 'Execute' in both the tool name and description, combined with the phrase 'action through the enforcement context', indicates this tool runs or triggers operations rather than merely reading or writing data. While deprecated, the tool remains capable of executing actions whose consequences are argument-dependent.

From the tool's definition Tool name 'execute_with_context' and description 'Execute an action through the enforcement context' explicitly indicate code/action execution.

Documented attack patterns abuse exactly the kind of access execute_with_context gives an agent:

POLICY

How to control execute_with_context

PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Passport System — Cryptographic Identity for AI Agents, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_with_context:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_with_context": {
      "limits": [
        {
          "counter": "execute_with_context_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

execute_with_context stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Agent Passport System — Cryptographic Identity for AI Agents — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Agent Passport System — Cryptographic Identity for AI Agents tools

Financial aps_aggregate_settlement Aggregate a batch of Attribution Primitives over a half-open settlement period [t0, t1) in Financial request_human_approval Request human approval for a high-value purchase. Destructive remove_intent_card Remove your IntentCard from the Intent Network. Use when your needs or offers have changed Destructive revoke_delegation [OPERATOR] Revoke a delegation. Optionally cascade to all sub-delegations. Destructive revoke_endorsement Revoke a principal's endorsement of an agent. 'I no longer authorize this agent.' Destructive aps_withdraw_provisional Commitment boundary: author withdraws their own provisional statement. Already-promoted st Execute aps_construct_attribution_primitive Build and sign a four-axis AttributionPrimitive for an action. Axes: D (data sources), P ( Execute commerce_preflight Run preflight checks before a purchase. Validates passport, delegation, merchant, and spen

All 150 Agent Passport System — Cryptographic Identity for AI Agents tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Agent Passport System — Cryptographic Identity for AI Agents → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about execute_with_context

What does the execute_with_context tool do? +

[deprecated in v3.0.0 — use gateway.aeoess.com REST API] Execute an action through the enforcement context. It is categorised as a Execute tool in the Agent Passport System — Cryptographic Identity for AI Agents MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does execute_with_context accept? +

execute_with_context accepts 4 parameters: scope, target, action_type, estimated_spend. Required: scope, target, action_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on execute_with_context? +

Register the Agent Passport System — Cryptographic Identity for AI Agents MCP server in PolicyLayer and add a rule for execute_with_context: 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 Agent Passport System — Cryptographic Identity for AI Agents. Nothing to install.

What risk level is execute_with_context? +

execute_with_context is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_with_context? +

Yes. Add a rate_limit block to the execute_with_context 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 execute_with_context completely? +

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

execute_with_context is provided by the Agent Passport System — Cryptographic Identity for AI Agents MCP server (https://mcp.aeoess.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Passport System — Cryptographic Identity for AI Agents tool call.

Start from Agent Passport System — Cryptographic Identity for AI Agents, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

150 Agent Passport System — Cryptographic Identity for AI Agents tools catalogued and risk-classified — across an index of 43,000+ MCP servers.