Fetch recent runtime logs from the project's log endpoint. Window is ±5 minutes around requestCreatedAt (ISO-8601, defaults to now). types: GATEWAY, ACTION_FLOW, ACTION_FLOW_NODE, ACTION_FLOW_CONTEXT_LOG, DEPLOYMENT, TPA, TRIGGER, SQL_GENERATION, GQL, ZAI. levels: INFO, WARNING, ERROR. customQuer...
AI agents call search_logs to retrieve information from Zion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
types | array | — | |
levels | array | — | |
appExId | string | null | — | |
projectExId | string | — | |
appVersionExId | string | null | — | |
requestCreatedAt | string | — | |
customQueryCondition | string | — |
Parameters from the server's own tool schema.
This tool retrieves and queries log data with no side effects. It supports filtering and searching within logs but does not create, modify, delete, or execute operations. The customQueryCondition parameter allows advanced filtering but remains a read operation. This is a standard observability/diagnostic tool with minimal blast radius.
From the tool's definition Tool 'Fetch recent runtime logs' with parameters for filtering by time window, log types, and levels. No modification, deletion, or execution capabilities described. Returns log data only.
Attacks that exploit this kind of access
Fetch recent runtime logs from the project's log endpoint. Window is ±5 minutes around requestCreatedAt (ISO-8601, defaults to now). types: GATEWAY, ACTION_FLOW, ACTION_FLOW_NODE, ACTION_FLOW_CONTEXT_LOG, DEPLOYMENT, TPA, TRIGGER, SQL_GENERATION, GQL, ZAI. levels: INFO, WARNING, ERROR. customQueryCondition is an Elasticsearch condition (e.g. 'traceId: "abc-123"'). It is categorised as a Read tool in the Zion MCP Server, which means it retrieves data without modifying state.
search_logs accepts 8 parameters: limit, types, levels, appExId, projectExId, appVersionExId, requestCreatedAt, customQueryCondition. The full parameter table on this page comes from the server's own tool schema.
Register the Zion MCP server in PolicyLayer and add a rule for search_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 Zion. Nothing to install.
search_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 search_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 search_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.
search_logs is provided by the Zion MCP server (zion-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 →