em_get_my_executions

Get tasks the agent has accepted/completed.

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-get-my-executions.md

What em_get_my_executions does on Execution Market

AI agents call em_get_my_executions 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_get_my_executions is rated Low

This tool retrieves information about an agent's own task execution history. It performs no writes, deletions, code execution, or financial operations. The 'get' verb and read-only semantics clearly indicate a Read category classification with low severity, as misuse would at worst expose only the agent's own task data.

From the tool's definition Tool name contains 'get_my_' and description states 'Get tasks the agent has accepted/completed' — a pure query operation that retrieves historical data without modification.

Questions about em_get_my_executions

What does the em_get_my_executions tool do? +

Get tasks the agent has accepted/completed. 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_get_my_executions? +

Register the Execution Market MCP server in PolicyLayer and add a rule for em_get_my_executions: 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_get_my_executions? +

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

Can I rate-limit em_get_my_executions? +

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

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

em_get_my_executions 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.