Get payment details needed to approve a task submission (Fase 1 mode). External agents use this to get the exact addresses and amounts they need to sign 2 EIP-3009 authorizations: one for the worker and one for the platform fee. Args: task_id: UUID of the task submission_id: UUID of the submissio...
Part of the Execution Market server.
Free to start. No card required.
AI agents call em_get_payment_info to retrieve information from Execution Market without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though em_get_payment_info only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"em_get_payment_info": {}
}
}See the full Execution Market policy for all 38 tools.
These attack patterns abuse exactly the kind of access em_get_payment_info gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get payment details needed to approve a task submission (Fase 1 mode). External agents use this to get the exact addresses and amounts they need to sign 2 EIP-3009 authorizations: one for the worker and one for the platform fee. Args: task_id: UUID of the task submission_id: UUID of the submission to approve Returns: JSON with worker_address, treasury_address, bounty_amount, fee_amount, token details, and signing parameters.. It is categorised as a Read tool in the Execution Market MCP Server, which means it retrieves data without modifying state.
Register the Execution Market MCP server in PolicyLayer and add a rule for em_get_payment_info: 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.
em_get_payment_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the em_get_payment_info 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.
Set action: deny in the PolicyLayer policy for em_get_payment_info. 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.
em_get_payment_info 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.
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.