AI agents call get_method_source_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 tool retrieves method source code from a Pharo class definition—a read-only operation that queries existing system information without side effects. It does not execute code, modify state, delete data, or move money. While it could expose sensitive logic, the risk is informational only and comparable to other introspection tools on this server (get_class_definition, get_class_comment).
From the tool's definition Tool name 'get_method_source_tool' and description 'Get the source code of a specific method in a Pharo class' indicate pure data retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get the source code of a specific method in a Pharo class. 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_method_source_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_method_source_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_method_source_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_method_source_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_method_source_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 →