em_server_status

Get the current status of the Execution Market MCP server and its integrations.

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-server-status.md

WHAT IT DOES

What em_server_status does on Execution Market

AI agents call em_server_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.

RISK

Why em_server_status is rated Low

This tool performs a status check/query operation that retrieves information about server health and integrations. It has no capability to modify data, execute code, delete resources, or move funds. The blast radius of misuse is minimal—an agent could only obtain status information. Status queries are typically safe read operations with no destructive or financial impact.

From the tool's definition Tool name 'em_server_status' and description 'Get the current status of the Execution Market MCP server and its integrations' indicate a read-only query operation that retrieves system state information without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs em_server_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Execution Market, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For em_server_status, this is the rule to start with:

em_server_status Allowed

em_server_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "em_server_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Execution Market, apply this rule, and every em_server_status call is checked against it from then on.

FAQ

Questions about em_server_status

What does the em_server_status tool do? +

Get the current status of the Execution Market MCP server and its integrations. 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_server_status? +

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

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

Can I rate-limit em_server_status? +

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

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

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

KEEP EXPLORING

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

This server

All 81 Execution Market tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →