em_escrow_status

A read tool on the Execution Market MCP server.

SERVERExecution Market SOURCEhttps://mcp.execution.market/mcp/
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/market-execution-execution-market/em-escrow-status.md

What em_escrow_status does on Execution Market

AI agents call em_escrow_status to retrieve information from Execution Market without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why em_escrow_status is rated Low

The tool name and naming pattern indicate this retrieves escrow state information rather than executing transactions, creating obligations, or modifying data. Status-checking tools typically have no side effects. While the empty description introduces some uncertainty, the strong naming signal and sibling context justify Read classification with medium-high confidence.

From the tool's definition Tool name 'em_escrow_status' implies querying or checking the state of escrow without modifying it. Context from sibling tool 'em_check_escrow_state' suggests status/state-checking operations are read-only queries. Description is empty, lowering confidence.

Questions about em_escrow_status

What does the em_escrow_status tool do? +

em_escrow_status is a read tool on the Execution Market MCP server. It is categorised as a Read tool in the Execution Market MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on em_escrow_status? +

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

What risk level is em_escrow_status? +

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

Can I rate-limit em_escrow_status? +

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

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

em_escrow_status is provided by the Execution Market MCP server (https://mcp.execution.market/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Execution Market, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Execution Market's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.