get_delx_reward_status
Check DELX/DRC reward status for an agent, including wallet binding, points, rank, and claimable epochs. Free
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/get-delx-reward-status.md
What get_delx_reward_status does on Delx Mcp A2a
AI agents call get_delx_reward_status to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | Yes | Stable Delx agent identifier |
agent_token | string | — | Agent identity token returned by /api/v1/agents/register; required for private reward status |
Parameters from the server's own tool schema.
Why get_delx_reward_status is rated Low
This tool retrieves and queries reward status data (wallet binding, points, rank, claimable epochs) with no side effects. The verb 'Check' and the lack of any modification language confirm this is a Read operation. The 'Free' designation indicates no financial transaction occurs. Severity is low because misuse would only expose reward information, not enable destructive, financial, or execution-based harm.
From the tool's definition Tool name 'get_delx_reward_status' and description 'Check DELX/DRC reward status for an agent, including wallet binding, points, rank, and claimable epochs' indicate a read-only query operation that retrieves reward information without modifying state.
Attacks that exploit this kind of access
The rule that runs get_delx_reward_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_delx_reward_status, this is the rule to start with:
get_delx_reward_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, apply this rule, and every get_delx_reward_status call is checked against it from then on.
Questions about get_delx_reward_status
Check DELX/DRC reward status for an agent, including wallet binding, points, rank, and claimable epochs. Free. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
get_delx_reward_status accepts 2 parameters: agent_id, agent_token. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for get_delx_reward_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 Delx Mcp A2a. Nothing to install.
get_delx_reward_status 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 get_delx_reward_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.
Set action: deny in the PolicyLayer policy for get_delx_reward_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.
get_delx_reward_status is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue