hives_query_deployment_logs
Query logs for a project (GET /v1/hives/projects/{project_id}/deployments/{deployment_id}/logs) [service status: down]
This record as markdown: /tools/lifesi-genesis-mcp/hives-query-deployment-logs.md
What hives_query_deployment_logs does on Genesis
AI agents call hives_query_deployment_logs to retrieve information from Genesis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | null | — | End time (defaults to now) |
page | integer | — | Page number (1-indexed) |
level | string | null | — | Filter by minimum log level |
start | string | null | — | Start time (defaults to 1 hour ago) |
search | string | null | — | Search query |
source | string | null | — | Filter by source (function, deployment, etc.) |
per_page | integer | — | Items per page |
project_id | string | Yes | Project ID |
request_id | string | null | — | Request ID for correlation |
deployment_id | string | Yes |
Parameters from the server's own tool schema.
Why hives_query_deployment_logs is rated Low
Even though hives_query_deployment_logs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs hives_query_deployment_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hives_query_deployment_logs, this is the rule to start with:
hives_query_deployment_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every hives_query_deployment_logs call is checked against it from then on.
Questions about hives_query_deployment_logs
Query logs for a project (GET /v1/hives/projects/{project_id}/deployments/{deployment_id}/logs) [service status: down]. It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.
hives_query_deployment_logs accepts 10 parameters: end, page, level, start, search, source, per_page, project_id, request_id, deployment_id. Required: project_id, deployment_id. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for hives_query_deployment_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 Genesis. Nothing to install.
hives_query_deployment_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 hives_query_deployment_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 hives_query_deployment_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.
hives_query_deployment_logs is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue