Get the Xero OAuth authorization URL.
AI agents call xero_get_auth_url to retrieve information from WWIDE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves an authentication URL, which is a read-only operation with no side effects on data or financial systems. The URL itself is public OAuth flow material. While it's part of an authentication flow, the tool itself does not perform authentication, create records, move money, execute commands, or delete data. It simply returns a URL for the user to visit.
From the tool's definition Tool name and description indicate it 'Get[s] the Xero OAuth authorization URL' — a retrieval operation that returns a URL for user authentication without modifying or executing operations on Xero data or accounts.
Attacks that exploit this kind of access
Get the Xero OAuth authorization URL. It is categorised as a Read tool in the WWIDE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WWIDE MCP Server MCP server in PolicyLayer and add a rule for xero_get_auth_url: 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 WWIDE MCP Server. Nothing to install.
xero_get_auth_url 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 xero_get_auth_url 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 xero_get_auth_url. 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.
xero_get_auth_url is provided by the WWIDE MCP Server MCP server (kulvir88/salesforce-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 →