neuron_webagent_get_run

Fetch one run's status, config snapshot and latest live stats (captured/flushed/leads/reels/hops/scrolls). status is running|stopped|completed|killed|stale.

SERVERNeuron SOURCEneuron-mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-webagent-get-run.md

WHAT IT DOES

What neuron_webagent_get_run does on Neuron

AI agents call neuron_webagent_get_run to retrieve information from Neuron without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`runId`	string	Yes	The agent-run id.

Parameters from the server's own tool schema.

RISK

Why neuron_webagent_get_run is rated Low

Even though neuron_webagent_get_run only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs neuron_webagent_get_run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_webagent_get_run, this is the rule to start with:

neuron_webagent_get_run Allowed

neuron_webagent_get_run is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_webagent_get_run": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_webagent_get_run call is checked against it from then on.

FAQ

Questions about neuron_webagent_get_run

What does the neuron_webagent_get_run tool do? +

Fetch one run's status, config snapshot and latest live stats (captured/flushed/leads/reels/hops/scrolls). status is running|stopped|completed|killed|stale. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.

What parameters does neuron_webagent_get_run accept? +

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

How do I enforce a policy on neuron_webagent_get_run? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_webagent_get_run: 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_webagent_get_run? +

neuron_webagent_get_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit neuron_webagent_get_run? +

Yes. Add a rate_limit block to the neuron_webagent_get_run 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_webagent_get_run completely? +

Set action: deny in the PolicyLayer policy for neuron_webagent_get_run. 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_webagent_get_run? +

neuron_webagent_get_run 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.

KEEP EXPLORING

More on Neuron, and thousands of servers like it.

This server

All 401 Neuron tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →