neuron_whoami
Check which Neuron account is currently logged in, including user name, email, role, and organization.
This record as markdown: /tools/io-github-conquext-neuron/neuron-whoami.md
What neuron_whoami does on Neuron
AI agents call neuron_whoami 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.
Why neuron_whoami is rated Low
This tool only retrieves identity and session information (name, email, role, organization) about the currently authenticated user. It has no side effects and cannot modify any data.
From the tool's definition Check which Neuron account is currently logged in, including user name, email, role, and organization
Attacks that exploit this kind of access
The rule that runs neuron_whoami 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_whoami, this is the rule to start with:
neuron_whoami is read-only, so it stays allowed. 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_whoami call is checked against it from then on.
Questions about neuron_whoami
Check which Neuron account is currently logged in, including user name, email, role, and organization. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_whoami: 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_whoami is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the neuron_whoami 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_whoami. 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_whoami 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