AI agents invoke run_sentinel_query to trigger actions in Security Copilot 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.
This tool executes arbitrary queries against a live security system (Microsoft Sentinel). The severity is high because: (1) it can query sensitive security logs and data across an organization, (2) query results could expose confidential information about incidents, vulnerabilities, or user activity, and (3) depending on KQL capabilities and permissions, certain queries might trigger alerts or actions.
From the tool's definition The tool is described as 'Run a query against Sentinel' (emphasis on run/execute). It enables execution of queries (likely KQL queries as mentioned in server description) against Microsoft Sentinel, a SIEM platform containing security events, logs, and…
Documented attack patterns abuse exactly the kind of access run_sentinel_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Security Copilot MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_sentinel_query:
{
"version": "1",
"default": "deny",
"tools": {
"run_sentinel_query": {
"limits": [
{
"counter": "run_sentinel_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_sentinel_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.
Free to start. No card required.
Run a query against Sentinel. It is categorised as a Execute tool in the Security Copilot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Security Copilot MCP Server MCP server in PolicyLayer and add a rule for run_sentinel_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 Security Copilot MCP Server. Nothing to install.
run_sentinel_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_sentinel_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.
Set action: deny in the PolicyLayer policy for run_sentinel_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.
run_sentinel_query is provided by the Security Copilot MCP Server MCP server (jguimera/securitycopilotmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Security Copilot 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 Security Copilot MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.