Execute a SQL query against an SLS project for log analysis and aggregation. Best for counting, grouping, statistical analysis. Example:
AI agents invoke query_logs_sql to trigger actions in Aliyun Sls. 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 runs arbitrary SQL queries against a log store. SQL execution can include aggregations, joins, and potentially destructive operations depending on what is permitted. Even if limited to SELECT-style analytics, executing arbitrary SQL is categorized as Execute due to the code-execution nature and potential for high blast radius if misused (e.g., expensive queries, data exfiltration).
From the tool's definition Execute a SQL query against an SLS project
Documented attack patterns abuse exactly the kind of access query_logs_sql gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Aliyun Sls, and nothing reaches the server without passing your rules. This is the rule we recommend for query_logs_sql:
{
"version": "1",
"default": "deny",
"tools": {
"query_logs_sql": {
"limits": [
{
"counter": "query_logs_sql_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}query_logs_sql 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.
Execute a SQL query against an SLS project for log analysis and aggregation. Best for counting, grouping, statistical analysis. Example:. It is categorised as a Execute tool in the Aliyun Sls MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aliyun Sls MCP server in PolicyLayer and add a rule for query_logs_sql: 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 Aliyun Sls. Nothing to install.
query_logs_sql 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 query_logs_sql 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 query_logs_sql. 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.
query_logs_sql is provided by the Aliyun Sls MCP server (suxyee/aliyun-sls-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Aliyun Sls, 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.
6 Aliyun Sls tools catalogued and risk-classified — across an index of 43,000+ MCP servers.