Reports whether PayRam blockchain listener workers are running and whether each chain’s RPC nodes
AI agents call check_node_sync to retrieve information from PayRam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the operational status of blockchain listener workers and RPC node connectivity. It has no side effects, does not trigger payment operations, does not modify data, and does not execute external commands. It is purely informational for diagnostics and monitoring.
From the tool's definition Tool description states it 'Reports whether PayRam blockchain listener workers are running and whether each chain's RPC nodes' — purely observational/diagnostic.
Documented attack patterns abuse exactly the kind of access check_node_sync gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PayRam MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_node_sync:
{
"version": "1",
"default": "deny",
"tools": {
"check_node_sync": {}
}
}check_node_sync is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reports whether PayRam blockchain listener workers are running and whether each chain’s RPC nodes. It is categorised as a Read tool in the PayRam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PayRam MCP Server MCP server in PolicyLayer and add a rule for check_node_sync: 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 PayRam MCP Server. Nothing to install.
check_node_sync 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 check_node_sync 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 check_node_sync. 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.
check_node_sync is provided by the PayRam MCP Server MCP server (payram/payram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 35 PayRam MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
35 PayRam MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.