get_instance_logs
AI agents call get_instance_logs to retrieve information from Morpheus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Log retrieval is a query operation that retrieves existing data without side effects. While the description is empty, the tool name and server context clearly indicate this fetches instance logs for monitoring/troubleshooting purposes. This poses minimal risk—an AI agent retrieving logs cannot directly harm infrastructure or data, though sensitive information in logs could be exposed.
From the tool's definition Tool name 'get_instance_logs' and context indicate retrieval of log data from cloud instances managed by Morpheus. No modification, deletion, or execution capabilities implied.
Attacks that exploit this kind of access
get_instance_logs. It is categorised as a Read tool in the Morpheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for get_instance_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 Morpheus MCP Server. Nothing to install.
get_instance_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_instance_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_instance_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_instance_logs is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). 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 →