crm_auth_url
Generate the OAuth authorization URL for connecting a CRM sub-account.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-auth-url.md
What crm_auth_url does on 0nmcp
AI agents call crm_auth_url to retrieve information from 0nmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crm_auth_url is rated Low
OAuth URL generation is a preparatory step in authentication that retrieves/generates a credential link without modifying state or triggering irreversible actions. It falls under Read category as it provides data (the URL) for downstream authentication flows without side effects of its own.
From the tool's definition Generate the OAuth authorization URL for connecting a CRM sub-account. The tool produces a URL needed to initiate OAuth flow, which is a read/retrieval operation that returns an authorization endpoint.
Attacks that exploit this kind of access
The rule that runs crm_auth_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_auth_url, this is the rule to start with:
crm_auth_url is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every crm_auth_url call is checked against it from then on.
Questions about crm_auth_url
Generate the OAuth authorization URL for connecting a CRM sub-account. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.
Register the 0n MCP server in PolicyLayer and add a rule for crm_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 0nmcp. Nothing to install.
crm_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 crm_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 crm_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.
crm_auth_url is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue