AI agents call get_signal_for_instance to retrieve information from Refinex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves query data about AWS spot price arbitrage signals for a specific instance. It has no side effects, does not modify state, and is consistent with other read-operation tools on the server. The empty description slightly reduces confidence, but the naming convention and server context strongly indicate a retrieval operation.
From the tool's definition Tool name 'get_signal_for_instance' follows read-like patterns (get_*). Server description indicates the tool retrieves 'live AWS spot price arbitrage signals' and 'suppression logs directly' with no mention of modification, deletion, or execution…
Attacks that exploit this kind of access
get_signal_for_instance. It is categorised as a Read tool in the Refinex MCP Server, which means it retrieves data without modifying state.
Register the Refinex MCP server in PolicyLayer and add a rule for get_signal_for_instance: 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 Refinex. Nothing to install.
get_signal_for_instance 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_signal_for_instance 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_signal_for_instance. 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_signal_for_instance is provided by the Refinex MCP server (keithrawlingsbrown/refinex-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 →