xano_get_workspace_details
AI agents call xano_get_workspace_details 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.
The tool appears designed to retrieve workspace information from the Xano Metadata API. Although the description is empty (lowering confidence slightly), the name strongly suggests a read-only query operation typical of metadata inspection. No evidence of data modification, deletion, code execution, or financial operations. Consistent with other 'browse' and 'get' tools on this server that retrieve information.
From the tool's definition Tool name 'xano_get_workspace_details' indicates a retrieval operation; 'get' and 'details' suggest querying workspace metadata without modification. No destructive or side-effect language present.
Attacks that exploit this kind of access
xano_get_workspace_details. 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_get_workspace_details: 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_get_workspace_details 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_get_workspace_details 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_get_workspace_details. 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_get_workspace_details 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 →