Low Risk

query_logs

Query log data from an SLS logstore with a time range and optional filter query. Returns formatted log entries. Use for debugging, error investigation, and log analysis. Supports SLS query syntax like

How to control query_logs ↓

What query_logs does on Aliyun Sls

AI agents call query_logs to retrieve information from Aliyun Sls without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why query_logs needs a policy

This tool retrieves and queries existing log data without side effects. It follows the Read category definition: 'retrieves or queries data; no side effects'. The time range and filter parameters are search/query arguments, not write or destructive operations. No evidence of execution capabilities, data modification, or irreversible actions.

From the tool's definition Tool description states it 'Query log data from an SLS logstore' and 'Returns formatted log entries' with purpose of 'debugging, error investigation, and log analysis'.

Documented attack patterns abuse exactly the kind of access query_logs gives an agent:

How to control query_logs

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:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_logs": {}
  }
}

query_logs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Aliyun Sls — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about query_logs

What does the query_logs tool do? +

Query log data from an SLS logstore with a time range and optional filter query. Returns formatted log entries. Use for debugging, error investigation, and log analysis. Supports SLS query syntax like. It is categorised as a Read tool in the Aliyun Sls MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_logs? +

Register the Aliyun Sls MCP server in PolicyLayer and add a rule for query_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 Aliyun Sls. Nothing to install.

What risk level is query_logs? +

query_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_logs? +

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

How do I block query_logs completely? +

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

What MCP server provides query_logs? +

query_logs 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.

Enforce policy on every Aliyun Sls tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.