Scan the local system for residue left behind by uninstalled
AI agents call prism_clean_scan to retrieve information from Prism Scanner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only scan to detect leftover files or registry entries from uninstalled software. It gathers information about the system state but does not execute commands, write data, delete files, or trigger external operations. The verb 'scan' combined with the context of detecting residue (rather than removing it) confirms this is a Read operation with minimal risk.
From the tool's definition Tool name 'prism_clean_scan' and description 'Scan the local system for residue left behind by uninstalled' indicates a scanning/querying operation that retrieves information about system state without modifying or deleting anything.
Attacks that exploit this kind of access
Scan the local system for residue left behind by uninstalled. It is categorised as a Read tool in the Prism Scanner MCP Server, which means it retrieves data without modifying state.
Register the Prism Scanner MCP server in PolicyLayer and add a rule for prism_clean_scan: 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 Prism Scanner. Nothing to install.
prism_clean_scan 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 prism_clean_scan 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 prism_clean_scan. 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.
prism_clean_scan is provided by the Prism Scanner MCP server (aidongise-cell/prism-scanner). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →