crm_decrypt_user_context
Decrypt encrypted user session data from a CRM marketplace app embed. Returns userId, companyId, locationId, email, role.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-decrypt-user-context.md
What crm_decrypt_user_context does on 0nmcp
AI agents call crm_decrypt_user_context 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_decrypt_user_context is rated Low
Although decryption is involved, the tool's function is purely to retrieve and expose encrypted session data. No data is created, modified, deleted, or destroyed. The high severity reflects the sensitive PII (email, userId, companyId, locationId, role) exposed if misused by an agent—an adversary could extract user context across the CRM marketplace—but this remains a Read operation.
From the tool's definition Tool name contains 'decrypt' and description states it 'Returns userId, companyId, locationId, email, role'—these are retrieval operations with no modification or deletion. The decryption is a read operation that extracts/queries existing session data.
Attacks that exploit this kind of access
The rule that runs crm_decrypt_user_context 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_decrypt_user_context, this is the rule to start with:
crm_decrypt_user_context 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_decrypt_user_context call is checked against it from then on.
Questions about crm_decrypt_user_context
Decrypt encrypted user session data from a CRM marketplace app embed. Returns userId, companyId, locationId, email, role. 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_decrypt_user_context: 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_decrypt_user_context 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_decrypt_user_context 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_decrypt_user_context. 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_decrypt_user_context 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