execute_log_insights_query

WHAT IT DOES

What execute_log_insights_query does on AWS Bedrock AgentCore MCP Server

AI agents invoke execute_log_insights_query to trigger actions in AWS Bedrock AgentCore MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_log_insights_query needs a policy

The 'execute' verb combined with 'log_insights_query' indicates this tool runs arbitrary or user-supplied queries against logging systems. Such execution can have wide-ranging effects depending on the query content and the data accessible to the underlying credentials.

From the tool's definition Tool name 'execute_log_insights_query' contains 'execute', indicating it runs queries against log data. AWS CloudWatch Logs Insights queries can extract, filter, and process log data, potentially exposing sensitive information depending on query construction…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_log_insights_query Rate-limited

execute_log_insights_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_log_insights_query": {
      "limits": [
        {
          "counter": "execute_log_insights_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AWS Bedrock AgentCore MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_log_insights_query

What does the execute_log_insights_query tool do? +

execute_log_insights_query. It is categorised as a Execute tool in the AWS Bedrock AgentCore MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_log_insights_query? +

Register the AWS Bedrock AgentCore MCP Server MCP server in PolicyLayer and add a rule for execute_log_insights_query: 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 AWS Bedrock AgentCore MCP Server. Nothing to install.

What risk level is execute_log_insights_query? +

execute_log_insights_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_log_insights_query? +

Yes. Add a rate_limit block to the execute_log_insights_query 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.

How do I block execute_log_insights_query completely? +

Set action: deny in the PolicyLayer policy for execute_log_insights_query. 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.

What MCP server provides execute_log_insights_query? +

execute_log_insights_query is provided by the AWS Bedrock AgentCore MCP Server MCP server (awslabs.amazon-bedrock-agentcore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.