crm_oauth_status
Show OAuth connection status for all CRM locations. Shows which have OAuth tokens and which are using PIT fallback.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-oauth-status.md
What crm_oauth_status does on 0nmcp
AI agents call crm_oauth_status 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_oauth_status is rated Low
This tool reads and displays authentication status information across CRM locations. It has no side effects, does not modify data, does not execute commands, and does not trigger external operations. The blast radius of misuse is minimal—an agent could view connection statuses but cannot alter configurations, delete data, or perform financial transactions. This is a clear Read category tool.
From the tool's definition The tool 'crm_oauth_status' performs a retrieval operation: 'Show OAuth connection status' and 'Shows which have OAuth tokens' — these are query/inspection operations with no modification of data or execution of operations.
Attacks that exploit this kind of access
The rule that runs crm_oauth_status 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_status, this is the rule to start with:
crm_oauth_status 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_oauth_status call is checked against it from then on.
Questions about crm_oauth_status
Show OAuth connection status for all CRM locations. Shows which have OAuth tokens and which are using PIT fallback. 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_oauth_status: 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_status 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_oauth_status 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_status. 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_status 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