Get recent container logs for a deployed app. Use this to debug apps that are failing or to verify an app started correctly after deploy_app.
AI agents call get_logs to retrieve information from Manifest MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing log data for diagnostic purposes. It does not create, modify, delete, or execute anything; it only reads and returns information. The context (debugging, verification) confirms this is a read-only operation with minimal blast radius.
From the tool's definition Tool name 'get_logs' and description 'Get recent container logs for a deployed app' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Get recent container logs for a deployed app. Use this to debug apps that are failing or to verify an app started correctly after deploy_app. It is categorised as a Read tool in the Manifest MCP MCP Server, which means it retrieves data without modifying state.
Register the Manifest MCP server in PolicyLayer and add a rule for get_logs: 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 Manifest MCP. Nothing to install.
get_logs 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_logs 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_logs. 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_logs is provided by the Manifest MCP server (manifest-network/manifest-mcp-mono). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →