xano_browse_request_history
AI agents call xano_browse_request_history to retrieve information from Xano MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or query request history logs from a Xano database. 'Browse' operations are fundamentally read-only with no side effects. Even with an empty description, the verb and context (sibling tools are clearly categorized as write/destructive/read) indicate this is a retrieval operation. Confidence is 0.8 rather than higher due to lack of explicit description, but the name is sufficiently clear.
From the tool's definition Tool name 'xano_browse_request_history' indicates browsing/querying historical data. The 'browse' verb is associated with read operations (list, fetch). No description provided, but naming pattern strongly suggests data retrieval without modification.
Attacks that exploit this kind of access
xano_browse_request_history. It is categorised as a Read tool in the Xano MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Xano MCP Server MCP server in PolicyLayer and add a rule for xano_browse_request_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 Xano MCP Server. Nothing to install.
xano_browse_request_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 xano_browse_request_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 xano_browse_request_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.
xano_browse_request_history is provided by the Xano MCP Server MCP server (roboulos/simple-xano-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 →