crm_marketplace_installer_details
Get installer details for a marketplace app — which locations have it installed, installation status, and configuration.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-marketplace-installer-details.md
What crm_marketplace_installer_details does on 0nmcp
AI agents call crm_marketplace_installer_details 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_marketplace_installer_details is rated Low
This tool queries and retrieves information about marketplace app installations without modifying, deleting, or executing anything. It is a passive read operation with no side effects. Severity is low because exposure of installation metadata poses minimal risk; an AI agent misusing this tool would only gain visibility into deployment information, not cause operational harm.
From the tool's definition Tool retrieves installer details—'Get installer details for a marketplace app — which locations have it installed, installation status, and configuration.' No modification, deletion, or execution of code/commands is described.
Attacks that exploit this kind of access
The rule that runs crm_marketplace_installer_details 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_marketplace_installer_details, this is the rule to start with:
crm_marketplace_installer_details 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_marketplace_installer_details call is checked against it from then on.
Questions about crm_marketplace_installer_details
Get installer details for a marketplace app — which locations have it installed, installation status, and configuration. 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_marketplace_installer_details: 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_marketplace_installer_details 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_marketplace_installer_details 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_marketplace_installer_details. 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_marketplace_installer_details 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