AI agents call get_neo_console_command_history_tool to retrieve information from Pharo Nc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries historical data from an existing console session. There are no modifications, deletions, code executions, or financial implications. The worst outcome of misuse would be unauthorized access to historical commands entered in the session, which has minimal blast radius since it only reveals what was previously executed, not enabling new harmful actions.
From the tool's definition The tool 'get_neo_console_command_history_tool' retrieves command history from a NeoConsole session. The description uses 'Get', indicating data retrieval with no side effects.
Attacks that exploit this kind of access
Get the command history from the current NeoConsole session. It is categorised as a Read tool in the Pharo Nc MCP Server, which means it retrieves data without modifying state.
Register the Pharo Nc MCP server in PolicyLayer and add a rule for get_neo_console_command_history_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 Pharo Nc. Nothing to install.
get_neo_console_command_history_tool 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 get_neo_console_command_history_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 get_neo_console_command_history_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.
get_neo_console_command_history_tool is provided by the Pharo Nc MCP server (mumez/pharo-nc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →