Low Risk

get_method_source

get_method_source

How to control get_method_source ↓

What get_method_source does on Pharo Smalltalk Interop

AI agents call get_method_source 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.

Low Risk

Why get_method_source needs a policy

This tool retrieves method source code from a Pharo Smalltalk image, which is a read-only query operation with no side effects. The absence of a description lowers confidence slightly, but the naming convention and sibling tools (get_class_comment, get_class_source) strongly indicate a retrieval function. No data is created, modified, deleted, or executed.

From the tool's definition Tool name is 'get_method_source' with no description provided. Based on the naming pattern and context (alongside similar read operations like 'get_class_comment', 'get_class_source', 'list_classes'), this retrieves source code without modification.

Documented attack patterns abuse exactly the kind of access get_method_source gives an agent:

How to control get_method_source

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 get_method_source:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_method_source": {}
  }
}

get_method_source is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Pharo Smalltalk Interop — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_method_source

What does the get_method_source tool do? +

get_method_source. It is categorised as a Read tool in the Pharo Smalltalk Interop MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_method_source? +

Register the Pharo Smalltalk Interop MCP server in PolicyLayer and add a rule for get_method_source: 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.

What risk level is get_method_source? +

get_method_source is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_method_source? +

Yes. Add a rate_limit block to the get_method_source 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.

How do I block get_method_source completely? +

Set action: deny in the PolicyLayer policy for get_method_source. 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.

What MCP server provides get_method_source? +

get_method_source 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.

Enforce policy on every Pharo Smalltalk Interop tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.