AI agents call get_reactor_list 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 retrieves and queries data about reactors without any side effects, modifications, or financial impact. The explicit 'READ-ONLY' designation and absence of wallet requirements confirm it performs passive information retrieval only. Low severity due to no blast radius from misuse.
From the tool's definition Tool is explicitly marked 'READ-ONLY' in description and performs listing operation ('List all known reactors') with no state modification. Returns informational data: reactor names, addresses, pool counts, status flags, and cooldown timers.
Attacks that exploit this kind of access
List all known reactors with fire-readiness status. READ-ONLY, no wallet needed. Returns each reactor name, address, pool count, whether it can be fired now, and cooldown remaining. 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 get_reactor_list: 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.
get_reactor_list 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_reactor_list 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_reactor_list. 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_reactor_list 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 →