neuron_refresh_token
Refresh the access token using a refresh token. Automatically sets the new access token for subsequent API calls.
This record as markdown: /tools/io-github-conquext-neuron/neuron-refresh-token.md
What neuron_refresh_token does on Neuron
AI agents use neuron_refresh_token to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
refreshToken | string | Yes | Refresh token obtained from the initial login response |
Parameters from the server's own tool schema.
Why neuron_refresh_token is rated Medium
This tool modifies authentication state by generating and setting a new access token. It creates/updates credentials used for subsequent API calls, making it a Write operation. Misuse could allow an attacker to maintain or hijack an authenticated session, but it does not directly delete data or execute arbitrary code.
From the tool's definition 'Refresh the access token using a refresh token. Automatically sets the new access token for subsequent API calls.'
Attacks that exploit this kind of access
The rule that runs neuron_refresh_token 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_refresh_token, this is the rule to start with:
neuron_refresh_token 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_refresh_token call is checked against it from then on.
Questions about neuron_refresh_token
Refresh the access token using a refresh token. Automatically sets the new access token for subsequent API calls. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_refresh_token accepts 1 parameter: refreshToken. Required: refreshToken. 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_refresh_token: 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_refresh_token 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 neuron_refresh_token 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_refresh_token. 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_refresh_token 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.
This server
Across the catalogue