List available log names and resource/source types for the selected scope
AI agents call list_log_sources to retrieve information from Logs Sieve without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries metadata about available log sources without executing queries, modifying logs, or triggering external operations. It simply enumerates available log names and resource types for the user to understand what data is queryable. This is a safe informational operation with minimal risk of misuse by an AI agent.
From the tool's definition The tool description explicitly states 'List available log names and resource/source types' — a pure retrieval operation with no mutation or side effects. The verb 'list' is a classic Read operation.
Attacks that exploit this kind of access
List available log names and resource/source types for the selected scope. It is categorised as a Read tool in the Logs Sieve MCP Server, which means it retrieves data without modifying state.
Register the Logs Sieve MCP server in PolicyLayer and add a rule for list_log_sources: 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 Logs Sieve. Nothing to install.
list_log_sources 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 list_log_sources 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 list_log_sources. 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.
list_log_sources is provided by the Logs Sieve MCP server (oluwatunmise-olat/mcp-server-logs-sieve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →