AI agents call nodus_get_signal to retrieve information from Nodusai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves market signals from an oracle service. While the service requires payment ($1 USDC) to obtain a session token, the tool itself merely queries and returns existing signal data without modifying, executing code, deleting data, or making financial transfers on behalf of the user. The financial transaction occurs upstream during authentication, not as a side effect of calling this tool.
From the tool's definition Tool description states 'Get an Oracle signal' which indicates data retrieval. No mutation, deletion, or execution of external operations is described.
Attacks that exploit this kind of access
Get an Oracle signal for a Polymarket or Kalshi prediction market. It is categorised as a Read tool in the Nodusai MCP Server, which means it retrieves data without modifying state.
Register the Nodusai MCP server in PolicyLayer and add a rule for nodus_get_signal: 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 Nodusai. Nothing to install.
nodus_get_signal 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 nodus_get_signal 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 nodus_get_signal. 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.
nodus_get_signal is provided by the Nodusai MCP server (nodusai-your-prediction-broker/nodusai-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 →