Low Risk

picnic_get_user_details

Get details of the current logged-in user

How to control picnic_get_user_details ↓

What picnic_get_user_details does on MCP Picnic

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

Low Risk

Why picnic_get_user_details needs a policy

This tool retrieves user profile information (name, address, payment methods, preferences, etc.) without modifying or deleting data. While classified as Read, severity is elevated to medium because user details can include personally identifiable information (PII), payment details, and delivery addresses that could be misused if an AI agent accesses them without proper authorization or shares them inappropriately.

From the tool's definition Tool name contains 'get' and description states 'Get details of the current logged-in user', indicating data retrieval without modification.

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

How to control picnic_get_user_details

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

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

picnic_get_user_details 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 MCP Picnic — 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.

Related tools and policies

Go deeper

Questions about picnic_get_user_details

What does the picnic_get_user_details tool do? +

Get details of the current logged-in user. It is categorised as a Read tool in the MCP Picnic MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on picnic_get_user_details? +

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

What risk level is picnic_get_user_details? +

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

Can I rate-limit picnic_get_user_details? +

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

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

picnic_get_user_details is provided by the MCP Picnic MCP server (ivo-toby/mcp-picnic). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Picnic tool call.

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

Free to start. No card required.

25 MCP Picnic tools catalogued and risk-classified — across an index of 43,000+ 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.