Build a documentation-backed research pack for a planned configuration or troubleshooting task.
AI agents call prepare_change_research to retrieve information from UserGate MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool gathers and compiles documentation information to support planning. It is analogous to other 'prepare_*_pack' tools on this server which appear to retrieve and package documentation. No side effects such as modifying configs, executing commands, or deleting data are implied.
From the tool's definition 'Build a documentation-backed research pack' and 'planned configuration or troubleshooting task' — assembles/retrieves documentation content; no indication of writing, executing, or destructive actions
Attacks that exploit this kind of access
Build a documentation-backed research pack for a planned configuration or troubleshooting task. It is categorised as a Read tool in the UserGate MCP MCP Server, which means it retrieves data without modifying state.
Register the UserGate MCP server in PolicyLayer and add a rule for prepare_change_research: 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 UserGate MCP. Nothing to install.
prepare_change_research 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 prepare_change_research 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 prepare_change_research. 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.
prepare_change_research is provided by the UserGate MCP server (neonsummit/usergate-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 →