Get the unified rolling chain refresher\
AI agents call get_refresher_status to retrieve information from Chains API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about a chain refresher process. It is a read-only operation that queries data with no side effects, mutations, or external command execution. The verb 'Get' and absence of any mutation or execution keywords confirm this is a Read category tool. Severity is low because retrieving status metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_refresher_status' and description 'Get the unified rolling chain refresher' indicate a query/retrieval operation. No modification, deletion, execution, or financial action is described.
Attacks that exploit this kind of access
Get the unified rolling chain refresher\. It is categorised as a Read tool in the Chains API MCP Server, which means it retrieves data without modifying state.
Register the Chains API MCP server in PolicyLayer and add a rule for get_refresher_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 Chains API. Nothing to install.
get_refresher_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_refresher_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_refresher_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_refresher_status is provided by the Chains API MCP server (johnaverse/chains-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →