Get user profile information by user_id Retrieves the complete user profile including both non-structured content and structured topics if available. Args: user_id: User identifier (required) Returns: JSON formatted string containing: - id: Profile ID - user_id: User identifier - profile_content:...
AI agents call get_user_profile to retrieve information from Mcp Oceanbase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation based on a user_id parameter. It has no side effects, does not modify any data, and simply queries and returns existing profile information. This is a straightforward Read operation with low severity since it only accesses user data without making changes or executing arbitrary code.
From the tool's definition Tool description states it 'Retrieves the complete user profile' and 'Returns JSON formatted string containing' profile data. No modification, deletion, or execution capabilities are indicated.
Documented attack patterns abuse exactly the kind of access get_user_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Oceanbase, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_profile:
{
"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.
Free to start. No card required.
Get user profile information by user_id Retrieves the complete user profile including both non-structured content and structured topics if available. Args: user_id: User identifier (required) Returns: JSON formatted string containing: - id: Profile ID - user_id: User identifier - profile_content: Profile text description - topics: Structured topics dictionary - created_at: Creation timestamp - updated_at: Last update timestamp Or error message if not found. It is categorised as a Read tool in the Mcp Oceanbase MCP Server, which means it retrieves data without modifying state.
Register the Mcp Oceanbase 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 Mcp Oceanbase. Nothing to install.
get_user_profile 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 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.
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.
get_user_profile is provided by the Mcp Oceanbase MCP server (oceanbase/awesome-oceanbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 134 Mcp Oceanbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
134 Mcp Oceanbase tools catalogued and risk-classified — across an index of 42,500+ MCP servers.