Search logs for a specific string and return context around matches
AI agents call get_coralogix_logs_by_string to retrieve information from Coralogix MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query on log data and returns results—a classic read operation. It does not create, modify, delete, or execute any operations beyond retrieving matching log entries. The sibling tools (get_2xx_logs, get_4xx_logs, get_5xx_logs) reinforce that this server is focused on log retrieval and analysis rather than log manipulation.
From the tool's definition Tool description states 'Search logs for a specific string and return context around matches'. The action is purely retrieving and querying log data with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access get_coralogix_logs_by_string gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Coralogix MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_coralogix_logs_by_string:
{
"version": "1",
"default": "deny",
"tools": {
"get_coralogix_logs_by_string": {}
}
}get_coralogix_logs_by_string 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.
Search logs for a specific string and return context around matches. It is categorised as a Read tool in the Coralogix MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Coralogix MCP Server MCP server in PolicyLayer and add a rule for get_coralogix_logs_by_string: 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 Coralogix MCP Server. Nothing to install.
get_coralogix_logs_by_string 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 get_coralogix_logs_by_string 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 get_coralogix_logs_by_string. 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.
get_coralogix_logs_by_string is provided by the Coralogix MCP Server MCP server (neoai-agent/coralogix-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Coralogix 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.
4 Coralogix MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.