get_user_profile

THE RISK

Low Risk

Why get_user_profile needs a policy

This tool retrieves user profile information without modifying, deleting, or executing operations. It is a straightforward read operation that queries existing data. The low severity reflects that exposing user profile data has limited blast radius compared to write, execute, or destructive operations, though confidence is slightly reduced due to the incomplete description provided.

From the tool's definition Tool name is 'get_user_profile' and description indicates it is triggered for 'queries', suggesting data retrieval without modification.

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

POLICY

How to control get_user_profile

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user_profile": {}
  }
}

get_user_profile 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 MemOS — 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 MemOS tools

Destructive delete_kb_documents Trigger: Use when specific documents in a Knowledge Base should be removed. Purpose: Del Destructive delete_memory Trigger: User explicitly asks to delete memories. Purpose: Delete memories by ID. STRI Destructive remove_knowledge_base Trigger: User requests to remove a Knowledge Base from the project. Purpose: Remove a Kn Write add_feedback Trigger: User wants to MODIFY/UPDATE memories, OR as the final step of a DELETION workflow Write add_kb_document Trigger: Use when the user provides document content, a file URL, or a local file path to Write add_message Trigger: 1. AUTO-INVOKED: After every answer to save dialogue history. 2. USER IN Write create_knowledge_base Trigger: When the user asks to create a project-specific or domain-specific Read get_kb_documents Trigger: Use to retrieve detailed information about specific documents in a Knowledge Base

All 10 MemOS 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 get_user_profile

What does the get_user_profile tool do? +

Trigger: MANDATORY for queries like. It is categorised as a Read tool in the MemOS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user_profile? +

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

What risk level is get_user_profile? +

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

Can I rate-limit get_user_profile? +

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

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

get_user_profile is provided by the MemOS MCP server (memtensor/memos-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MemOS tool call.

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

CHECK YOUR STACK →