Low Risk

get_username_from_user_id

Get the Instagram username for a given user ID. Args: user_id: Instagram user ID. Returns: A dictionary with success status and the username or error message.

How to control get_username_from_user_id ↓

AI agents call get_username_from_user_id to retrieve information from Instagram DM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This is a simple data retrieval tool that maps a user ID to a username. It queries existing data without modifying state, triggering actions, or committing resources. The blast radius of misuse is minimal—an attacker could discover usernames from IDs they already possess, but this is low-impact reconnaissance. Classified as Read with low severity.

From the tool's definition Tool performs a lookup/retrieval operation ("Get the Instagram username") with no side effects. Returns data without modifying, deleting, or executing actions.

Documented attack patterns abuse exactly the kind of access get_username_from_user_id gives an agent:

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_username_from_user_id": {}
  }
}

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

  1. Create a free account and register Instagram DM MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_username_from_user_id tool do? +

Get the Instagram username for a given user ID. Args: user_id: Instagram user ID. Returns: A dictionary with success status and the username or error message. It is categorised as a Read tool in the Instagram DM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_username_from_user_id? +

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

What risk level is get_username_from_user_id? +

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

Can I rate-limit get_username_from_user_id? +

Yes. Add a rate_limit block to the get_username_from_user_id 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 get_username_from_user_id completely? +

Set action: deny in the PolicyLayer policy for get_username_from_user_id. 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 get_username_from_user_id? +

get_username_from_user_id is provided by the Instagram DM MCP Server MCP server (trypeggy/instagram_dm_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Instagram DM MCP Server tool call.

Deterministic rules across all 25 Instagram DM MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

25 Instagram DM MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.