get_changelog
AI agents call get_changelog to retrieve information from Reflex Docs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves changelog information from Reflex documentation. This is a read-only operation that queries existing data without modifying, deleting, or executing any code. The empty description is mitigated by strong context from the server's stated capabilities (changelog is explicitly mentioned) and the tool's name pattern matching other safe retrieval tools on the server (get_doc, get_migration_guide, etc.).
From the tool's definition Tool name 'get_changelog' combined with server description stating it retrieves documentation including 'changelog' — this is a retrieval/read operation with no side effects.
Attacks that exploit this kind of access
get_changelog. It is categorised as a Read tool in the Reflex Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Reflex Docs MCP Server MCP server in PolicyLayer and add a rule for get_changelog: 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 Reflex Docs MCP Server. Nothing to install.
get_changelog 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_changelog 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_changelog. 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_changelog is provided by the Reflex Docs MCP Server MCP server (itsmeadarsh2008/reflex-docs-mcp). 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 →