38 tools. 15 can modify or destroy data without limits.
5 destructive tools with no built-in limits. Policy required.
Last updated:
Free to start. No card required.
Full per-tool breakdown → Model it in the token calculator →
Financial operations (em_escrow_charge, em_escrow_refund, em_withdraw_earnings) can move real money. An agent caught in a loop could drain accounts before anyone notices.
Destructive tools (em_cancel_task, em_escrow_release) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (em_apply_to_task, em_approve_submission, em_assign_task) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
{
"em_escrow_charge": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
} Financial tools should be explicitly enabled per use case, not open by default.
{
"em_cancel_task": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"em_apply_to_task": {
"limits": [
{
"counter": "em_apply_to_task_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"em_accept_agent_task": {
"limits": [
{
"counter": "em_accept_agent_task_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Execution Market server exposes 3 financial tools including em_escrow_charge, em_escrow_refund, em_withdraw_earnings. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.
Yes. The Execution Market server exposes 2 destructive tools including em_cancel_task, em_escrow_release. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
The Execution Market server has 10 write tools including em_apply_to_task, em_approve_submission, em_assign_task. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Execution Market.
38 tools across 4 categories: Destructive, Financial, Read, Write. 23 are read-only. 15 can modify, create, or delete data.
Register the Execution Market MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Starter policies for each. Same risk classification, live on your fleet in minutes.
Deterministic rules across all 38 Execution Market 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.