modal_search_logs
AI agents call modal_search_logs to retrieve information from Modal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches logs, a read-only query operation that retrieves data without side effects. The server explicitly advertises itself as read-only and non-mutating. The empty description prevents higher confidence, but contextual evidence from the server's stated scope and sibling tools strongly indicates this is a data retrieval tool.
From the tool's definition Tool name 'modal_search_logs' combined with server description stating 'read-only Modal context' and explicit commitment to not granting 'mutation tools'.
Attacks that exploit this kind of access
modal_search_logs. It is categorised as a Read tool in the Modal MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Modal MCP Server MCP server in PolicyLayer and add a rule for modal_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 Modal MCP Server. Nothing to install.
modal_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 modal_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 modal_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.
modal_search_logs is provided by the Modal MCP Server MCP server (php-workx/modal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
modal_search_logs is one line of Modal MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →