AI agents call get_settings 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 retrieves settings from the Pharo Smalltalk image without altering state. This is consistent with Read operations (get, fetch). Although the description is empty, the naming convention and context of sibling tools strongly suggest a non-destructive query operation. Confidence is high but slightly reduced due to the missing description.
From the tool's definition Tool named 'get_settings' with no description provided. Given the name and sibling tools like 'get_class_comment' and 'get_class_source' which are clearly Read operations, 'get_settings' appears to retrieve configuration or state data without modification.
Documented attack patterns abuse exactly the kind of access get_settings 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 get_settings:
{
"version": "1",
"default": "deny",
"tools": {
"get_settings": {}
}
}get_settings 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.
get_settings. 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 get_settings: 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.
get_settings 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_settings 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_settings. 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_settings 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.