Get logs for a stack (all services combined, no per-service filtering).
AI agents call get_stack_log to retrieve information from Komodo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical log information from a deployed stack. Logs are read-only data artifacts that reflect past events. There is no creation, modification, deletion, or execution of external systems—only passive observation of existing data. The blast radius is minimal; misuse would at worst expose information already generated by the platform.
From the tool's definition Tool name 'get_stack_log' and description 'Get logs for a stack' indicate a retrieval operation that queries and returns log data without modification or execution.
Documented attack patterns abuse exactly the kind of access get_stack_log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Komodo, and nothing reaches the server without passing your rules. This is the rule we recommend for get_stack_log:
{
"version": "1",
"default": "deny",
"tools": {
"get_stack_log": {}
}
}get_stack_log 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 logs for a stack (all services combined, no per-service filtering). It is categorised as a Read tool in the Komodo MCP Server, which means it retrieves data without modifying state.
Register the Komodo MCP server in PolicyLayer and add a rule for get_stack_log: 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 Komodo. Nothing to install.
get_stack_log 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_stack_log 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_stack_log. 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_stack_log is provided by the Komodo MCP server (myrikld/komodo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Komodo, 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.
53 Komodo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.