get_config_history_detail_tool
AI agents call get_config_history_detail_tool to retrieve information from MCP Logback Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to fetch historical configuration details from a logback analyzer system. Retrieval operations that query existing data without side effects classify as Read category. Severity is low because it accesses configuration/history metadata with no capability to alter system state, execute operations, or cause irreversible changes.
From the tool's definition Tool name contains 'get' prefix and 'history_detail', indicating data retrieval. The empty description prevents fuller assessment, but naming convention and sibling tools (get_config_tool, get_latest_history_tool) suggest this retrieves configuration or…
Attacks that exploit this kind of access
get_config_history_detail_tool. It is categorised as a Read tool in the MCP Logback Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Logback Analyzer MCP server in PolicyLayer and add a rule for get_config_history_detail_tool: 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 Logback Analyzer. Nothing to install.
get_config_history_detail_tool 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_config_history_detail_tool 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_config_history_detail_tool. 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_config_history_detail_tool is provided by the MCP Logback Analyzer MCP server (mengbi-super/mcp-tools). 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 →