AI agents call unrugable_check_reactor to retrieve information from Baselings without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a lookup operation to verify if an address matches certain criteria (registered reactor status). It has no side effects, does not create, modify, or delete data, and does not execute financial transactions or arbitrary code. It is a straightforward read/query operation with minimal blast radius if misused by an agent.
From the tool's definition Tool description states 'Check whether an address is a registered Unrugable reactor' — a query operation that retrieves/validates information about an address without modifying state or executing transactions.
Attacks that exploit this kind of access
Check whether an address is a registered Unrugable reactor (valid target for invite links). It is categorised as a Read tool in the Baselings MCP Server, which means it retrieves data without modifying state.
Register the Baselings MCP server in PolicyLayer and add a rule for unrugable_check_reactor: 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 Baselings. Nothing to install.
unrugable_check_reactor 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 unrugable_check_reactor 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 unrugable_check_reactor. 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.
unrugable_check_reactor is provided by the Baselings MCP server (jimbo530/baselings-mcp). 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 →