Fetch logs for a Runtime Manager deployment. Call runtime_list_deployments first to obtain the deploymentId.
AI agents call runtime_get_logs to retrieve information from Anypoint MCP Server 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 data from a deployment—a pure read operation. Fetching logs does not modify, delete, or execute anything; it only queries and returns existing data. The severity is low because log access, while potentially sensitive depending on log content, does not directly impact system state or operations.
From the tool's definition Tool name 'runtime_get_logs' and description 'Fetch logs for a Runtime Manager deployment' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch logs for a Runtime Manager deployment. Call runtime_list_deployments first to obtain the deploymentId. It is categorised as a Read tool in the Anypoint MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Anypoint MCP Server MCP server in PolicyLayer and add a rule for runtime_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 Anypoint MCP Server. Nothing to install.
runtime_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 runtime_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 runtime_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.
runtime_get_logs is provided by the Anypoint MCP Server MCP server (sravannerella/mulesoft-mcp-server). 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 →