Returns the whole record of a log with the given ID
AI agents call getLogDetail to retrieve information from Google Cloud Logging 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 and queries log data without side effects. It falls squarely into the Read category as it only fetches existing log entries by ID. The severity is low because log data retrieval poses minimal risk—logs typically contain observability information and are already intended to be readable by authorized users. No modifications, deletions, or external operations are possible with this tool.
From the tool's definition Tool 'getLogDetail' returns log records with no ability to modify, delete, or execute operations. Description states it 'returns the whole record of a log' which is purely a retrieval operation.
Documented attack patterns abuse exactly the kind of access getLogDetail gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Cloud Logging MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getLogDetail:
{
"version": "1",
"default": "deny",
"tools": {
"getLogDetail": {}
}
}getLogDetail 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.
Returns the whole record of a log with the given ID. It is categorised as a Read tool in the Google Cloud Logging MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Cloud Logging MCP Server MCP server in PolicyLayer and add a rule for getLogDetail: 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 Google Cloud Logging MCP Server. Nothing to install.
getLogDetail 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 getLogDetail 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 getLogDetail. 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.
getLogDetail is provided by the Google Cloud Logging MCP Server MCP server (swen128/cloud-logging-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Cloud Logging MCP Server, 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.
3 Google Cloud Logging MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.