AI agents call container_topology to retrieve information from MCP SSH SRE without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves container topology information (relationships, structure, dependencies) without modifying system state. Despite the vague description, the explicit read-only design of the MCP SSH SRE server and the monitoring/diagnostic context indicate this performs queries only. Even if it executes a topology discovery operation, that's a diagnostic read operation with no side effects or data mutations.
From the tool's definition Tool name 'container_topology' combined with server description stating 'read-only server monitoring and diagnostic tools' and 'container management' capabilities. The 'ops' suffix refers to operations/queries rather than modifications.
Documented attack patterns abuse exactly the kind of access container_topology gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP SSH SRE, and nothing reaches the server without passing your rules. This is the rule we recommend for container_topology:
{
"version": "1",
"default": "deny",
"tools": {
"container_topology": {}
}
}container_topology 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.
Container topology ops. It is categorised as a Read tool in the MCP SSH SRE MCP Server, which means it retrieves data without modifying state.
Register the MCP SSH SRE MCP server in PolicyLayer and add a rule for container_topology: 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 MCP SSH SRE. Nothing to install.
container_topology 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 container_topology 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 container_topology. 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.
container_topology is provided by the MCP SSH SRE MCP server (jeprecated/mcp-ssh-sre). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP SSH SRE, 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.
13 MCP SSH SRE tools catalogued and risk-classified — across an index of 43,000+ MCP servers.