user-info

THE RISK

Low Risk

Why user-info needs a policy

This tool only queries and returns user information without creating, modifying, deleting, or executing operations. It is purely informational retrieval, fitting the Read category. Severity is low because user metadata retrieval poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'user-info' and description 'Retrieve information about a user' indicate a data retrieval operation with no side effects. The phrase 'returns the current user' confirms it fetches existing data without modification.

Documented attack patterns abuse exactly the kind of access user-info gives an agent:

POLICY

How to control user-info

PolicyLayer is an MCP gateway — it sits between your AI agents and Dynamic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for user-info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "user-info": {}
  }
}

user-info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Dynamic MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dynamic MCP Server tools

Destructive delete-prompt Delete a prompt from the system Destructive delete-tool Delete a tool Destructive delete-user Delete a user Destructive remove-user Remove (delete) a user by email. This action is irreversible. You must confirm with the us Write reset-api-key Reset a user Write add-prompt Add a new prompt to the system Write add-user Add a new user Write hide-tool Hide one or more tools for the current user

All 18 Dynamic MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about user-info

What does the user-info tool do? +

Retrieve information about a user. If email is omitted, returns the current user. It is categorised as a Read tool in the Dynamic MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on user-info? +

Register the Dynamic MCP Server MCP server in PolicyLayer and add a rule for user-info: 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 Dynamic MCP Server. Nothing to install.

What risk level is user-info? +

user-info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit user-info? +

Yes. Add a rate_limit block to the user-info 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.

How do I block user-info completely? +

Set action: deny in the PolicyLayer policy for user-info. 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.

What MCP server provides user-info? +

user-info is provided by the Dynamic MCP Server MCP server (scitara-cto/dynamic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dynamic MCP Server tool call.

Start from Dynamic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →