list_wakeup_targets_by_address

Use this to list WAITING XDaLa runtime steps that the given wallet or Safe address is allowed to wake via RPC. This is read-only and calls xgr_listWakeupTargetsByAddress, then enriches public/plain XRC rule payload metadata via eth_call when available.

Server XGR MCP Gateway xgr-network/xgr-mcp
Category Read
Risk class Low
Parameters 00 required

What list_wakeup_targets_by_address does on XGR MCP Gateway

AI agents call list_wakeup_targets_by_address to retrieve information from XGR MCP Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_wakeup_targets_by_address needs a policy

The tool retrieves and queries XDaLa runtime steps and rule metadata for a given address without creating, modifying, deleting, or executing any on-chain actions. It is purely informational, making it a Read category risk with low severity due to minimal blast radius from misuse.

From the tool's definition Tool description explicitly states 'This is read-only' and 'list' operations are retrievals with no side effects. The operation calls 'xgr_listWakeupTargetsByAddress' to query blockchain data and enriches it via 'eth_call', both query operations.

Questions about list_wakeup_targets_by_address

What does the list_wakeup_targets_by_address tool do? +

Use this to list WAITING XDaLa runtime steps that the given wallet or Safe address is allowed to wake via RPC. This is read-only and calls xgr_listWakeupTargetsByAddress, then enriches public/plain XRC rule payload metadata via eth_call when available. It is categorised as a Read tool in the XGR MCP Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_wakeup_targets_by_address? +

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

What risk level is list_wakeup_targets_by_address? +

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

Can I rate-limit list_wakeup_targets_by_address? +

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

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

list_wakeup_targets_by_address is provided by the XGR MCP Gateway MCP server (xgr-network/xgr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.