AI agents call nodus_query_history 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 and displays past query records belonging to the user. It is a read-only operation that queries stored history without creating, modifying, deleting, or executing any external operations. The blast radius is minimal—exposure would reveal what queries a user has made but poses no financial, destructive, or execution risk.
From the tool's definition Tool name 'nodus_query_history' and description 'View your recent NodusAI oracle query history' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
View your recent NodusAI oracle query history. 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_query_history: 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_query_history 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_query_history 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_query_history. 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_query_history 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 →