AI agents use export_report to create or update resources in Memory Shell Detector MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory Shell Detector MCP environment.
Based on the tool name alone, 'export_report' likely generates and writes a report file to disk. In the context of a memory shell detector, this would be a Write operation (creating a report file). However, with no description available, confidence is low. Severity is medium because exporting reports could potentially expose sensitive system scan data or be written to unintended locations.
From the tool's definition Tool name 'export_report'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access export_report 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 export_report:
{
"version": "1",
"default": "deny",
"tools": {
"export_report": {
"limits": [
{
"counter": "export_report_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_report stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
export_report. It is categorised as a Write tool in the Memory Shell Detector MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory Shell Detector MCP server in PolicyLayer and add a rule for export_report: 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.
export_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_report 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 export_report. 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.
export_report 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.