neuron_test_tool
Execute a dry-run test of a custom API tool with sample arguments to verify the endpoint responds correctly.
This record as markdown: /tools/io-github-conquext-neuron/neuron-test-tool.md
What neuron_test_tool does on Neuron
AI agents invoke neuron_test_tool to trigger actions in Neuron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the tool to test |
args | object | Yes | Sample arguments object to pass to the tool for testing |
Parameters from the server's own tool schema.
Why neuron_test_tool is rated High
The tool actively executes calls against an external API endpoint (even if labeled 'dry-run'), triggering real network requests and external operations. This qualifies as Execute since it runs external operations whose effects depend on arguments. Severity is medium because while it's framed as a test, it still contacts external endpoints and could cause unintended side effects depending on the target API.
From the tool's definition Execute a dry-run test of a custom API tool with sample arguments to verify the endpoint responds correctly
Attacks that exploit this kind of access
The rule that runs neuron_test_tool 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_test_tool, this is the rule to start with:
neuron_test_tool stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_test_tool call is checked against it from then on.
Questions about neuron_test_tool
Execute a dry-run test of a custom API tool with sample arguments to verify the endpoint responds correctly. It is categorised as a Execute tool in the Neuron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
neuron_test_tool accepts 2 parameters: id, args. Required: id, args. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_test_tool: 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.
neuron_test_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the neuron_test_tool 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 neuron_test_tool. 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.
neuron_test_tool 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.
Across the catalogue