Retrieve log lines before and after a specific log entry using its pack_id and pack_meta. First query logs with query_logs to find a log entry, then use its __tag__:__pack_id__ and __tag__:__pack_meta__ fields to get surrounding context. Useful for understanding full execution flow around an error.
AI agents call get_context_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.
This tool queries existing log data to provide contextual information around a specific log entry. It performs a read-only operation on log storage with no side effects, data modification, deletion, or code execution. The severity is low because log retrieval poses minimal risk—it accesses already-stored diagnostic data without altering system state or performing destructive actions.
From the tool's definition Tool retrieves context logs around a specific entry using pack_id and pack_meta; description emphasizes 'Retrieve log lines' and 'get surrounding context' with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_context_logs 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 get_context_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_context_logs": {}
}
}get_context_logs 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.
Retrieve log lines before and after a specific log entry using its pack_id and pack_meta. First query logs with query_logs to find a log entry, then use its __tag__:__pack_id__ and __tag__:__pack_meta__ fields to get surrounding context. Useful for understanding full execution flow around an error. It is categorised as a Read tool in the Aliyun Sls MCP Server, which means it retrieves data without modifying state.
Register the Aliyun Sls MCP server in PolicyLayer and add a rule for get_context_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.
get_context_logs 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_context_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.
Set action: deny in the PolicyLayer policy for get_context_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.
get_context_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.
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.