Get details about a specific log source.
AI agents call get_log_source to retrieve information from MCP Log Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a log source configuration or details. It performs a query/fetch operation with no side effects, fitting the Read category. The severity is low because reading log source metadata poses minimal risk—it cannot modify systems, delete data, or execute code. Confidence is high because the action is straightforward: getting (retrieving) details without alteration.
From the tool's definition Tool name 'get_log_source' and description 'Get details about a specific log source' indicate retrieval of metadata about a log source with no modification or deletion.
Attacks that exploit this kind of access
Get details about a specific log source. It is categorised as a Read tool in the MCP Log Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Log Analyzer MCP server in PolicyLayer and add a rule for get_log_source: 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 MCP Log Analyzer. Nothing to install.
get_log_source 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_log_source 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_log_source. 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_log_source is provided by the MCP Log Analyzer MCP server (sedwardstx/demomcp). 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 →