AI agents call list_methods to retrieve information from Pharo Smalltalk Interop without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or enumerate methods (a read operation) based on its name. While the description is empty (lowering confidence slightly), the naming convention and context of sibling tools (get_class_source, get_method_source) strongly suggest this is a query/list operation. The blast radius of misuse is minimal—an agent could enumerate the codebase but cannot modify, execute code, delete, or move funds.
From the tool's definition Tool name 'list_methods' with no description suggests listing/querying methods in a Pharo Smalltalk image; no modification, deletion, or execution indicated by the name alone.
Documented attack patterns abuse exactly the kind of access list_methods gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pharo Smalltalk Interop, and nothing reaches the server without passing your rules. This is the rule we recommend for list_methods:
{
"version": "1",
"default": "deny",
"tools": {
"list_methods": {}
}
}list_methods is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_methods. It is categorised as a Read tool in the Pharo Smalltalk Interop MCP Server, which means it retrieves data without modifying state.
Register the Pharo Smalltalk Interop MCP server in PolicyLayer and add a rule for list_methods: 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 Smalltalk Interop. Nothing to install.
list_methods 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 list_methods 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 list_methods. 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.
list_methods is provided by the Pharo Smalltalk Interop MCP server (mumez/pharo-smalltalk-interop-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pharo Smalltalk Interop, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Pharo Smalltalk Interop tools catalogued and risk-classified — across an index of 43,000+ MCP servers.