AI agents call scan_process to retrieve information from Memory Shell Detector MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite empty description, context from sibling tools and server purpose strongly indicates scan_process performs process inspection/analysis without modification. This is a Read operation.
From the tool's definition Tool name is 'scan_process' which implies reading/querying Java process state. Sibling tools like 'list_java_processes', 'view_class_code', and 'get_system_info_tool' are clearly Read operations.
Documented attack patterns abuse exactly the kind of access scan_process gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory Shell Detector MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for scan_process:
{
"version": "1",
"default": "deny",
"tools": {
"scan_process": {}
}
}scan_process is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
scan_process. It is categorised as a Read tool in the Memory Shell Detector MCP MCP Server, which means it retrieves data without modifying state.
Register the Memory Shell Detector MCP server in PolicyLayer and add a rule for scan_process: 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 Memory Shell Detector MCP. Nothing to install.
scan_process 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 scan_process 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 scan_process. 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.
scan_process is provided by the Memory Shell Detector MCP server (ruoji6/memory-shell-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memory Shell Detector MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Memory Shell Detector MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.