search_project_logs
Search for specific patterns or errors in project logs
This record as markdown: /tools/caravanglory-cocos-mcp-server/search-project-logs.md
What search_project_logs does on Cocos
AI agents call search_project_logs to retrieve information from Cocos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_project_logs is rated Low
Searching project logs is a read-only operation with no side effects. It retrieves and filters existing log data but does not modify, delete, execute code, or affect project state. The low severity reflects minimal blast radius even if misused by an AI agent, as it cannot cause damage beyond accessing log information that developers would normally review.
From the tool's definition Tool name is 'search_project_logs' and description states it 'Search[es] for specific patterns or errors in project logs' — this is a query/search operation that retrieves log data without modification or execution.
Attacks that exploit this kind of access
The rule that runs search_project_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cocos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_project_logs, this is the rule to start with:
search_project_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 Cocos, apply this rule, and every search_project_logs call is checked against it from then on.
Questions about search_project_logs
Search for specific patterns or errors in project logs. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.
Register the Cocos MCP server in PolicyLayer and add a rule for search_project_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 Cocos. Nothing to install.
search_project_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_project_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_project_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_project_logs is provided by the Cocos MCP server (caravanglory/cocos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cocos, and thousands of servers like it.
This server
Across the catalogue