crm_oauth_connect
Store OAuth tokens for a CRM location after OAuth callback. This enables auto-auth for all CRM tools on that location.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-oauth-connect.md
What crm_oauth_connect does on 0nmcp
AI agents use crm_oauth_connect to create or update resources in 0nmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0nmcp environment.
Why crm_oauth_connect is rated Medium
This tool writes OAuth tokens to persistent storage, which is a reversible data modification. While it doesn't delete or destroy data (so not Destructive) and doesn't execute arbitrary code (so not Execute), it creates/modifies authentication secrets that grant broad access ('for all CRM tools on that location').
From the tool's definition The tool description explicitly states it 'stores OAuth tokens' and 'enables auto-auth for all CRM tools on that location.' Storing authentication credentials is a reversible write operation that creates or modifies sensitive data.
Attacks that exploit this kind of access
The rule that runs crm_oauth_connect 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_oauth_connect, this is the rule to start with:
crm_oauth_connect stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_oauth_connect call is checked against it from then on.
Questions about crm_oauth_connect
Store OAuth tokens for a CRM location after OAuth callback. This enables auto-auth for all CRM tools on that location. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 0n MCP server in PolicyLayer and add a rule for crm_oauth_connect: 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_oauth_connect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crm_oauth_connect 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_oauth_connect. 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_oauth_connect 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