New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

neuron_storage_job

Status and result of a clear-media / clear-chat job started by neuron_clear_media or neuron_clear_chat.

SERVERNeuron SOURCEneuron-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 11 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-storage-job.md

What neuron_storage_job does on Neuron

AI agents call neuron_storage_job to permanently remove resources in Neuron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
jobId string Yes

Parameters from the server's own tool schema.

Why neuron_storage_job is rated Critical

An AI agent that decides to call neuron_storage_job doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Neuron is gone. There is no undo for destructive operations.

Questions about neuron_storage_job

What does the neuron_storage_job tool do? +

Status and result of a clear-media / clear-chat job started by neuron_clear_media or neuron_clear_chat. It is categorised as a Destructive tool in the Neuron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does neuron_storage_job accept? +

neuron_storage_job accepts 1 parameter: jobId. Required: jobId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_storage_job? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_storage_job: 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 Neuron. Nothing to install.

What risk level is neuron_storage_job? +

neuron_storage_job is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit neuron_storage_job? +

Yes. Add a rate_limit block to the neuron_storage_job 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.

How do I block neuron_storage_job completely? +

Set action: deny in the PolicyLayer policy for neuron_storage_job. 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.

What MCP server provides neuron_storage_job? +

neuron_storage_job is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Neuron, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Neuron's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.