AI agents call remember_admin_inspect_user_ghost_configs to retrieve information from Remember without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves (inspects) user configuration data without modifying it, placing it in the Read category. Severity is high rather than low because: (1) it is an admin-level tool with elevated privileges accessing multi-tenant data, (2) it can expose sensitive user configurations including potentially authentication-related settings ('ghost_configs' terminology), and (3) in a multi-tenant system, unauthorized…
From the tool's definition Tool name contains 'inspect' and description states '[Admin] Inspect a user', indicating it retrieves user configuration data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
[Admin] Inspect a user. It is categorised as a Read tool in the Remember MCP Server, which means it retrieves data without modifying state.
Register the Remember MCP server in PolicyLayer and add a rule for remember_admin_inspect_user_ghost_configs: 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 Remember. Nothing to install.
remember_admin_inspect_user_ghost_configs 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 remember_admin_inspect_user_ghost_configs 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 remember_admin_inspect_user_ghost_configs. 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.
remember_admin_inspect_user_ghost_configs is provided by the Remember MCP server (@prmichaelsen/remember-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 →