Low Risk

list_available_personal_info

List all available personal information within current permissions

How to control list_available_personal_info ↓

What list_available_personal_info does on Personal Context MCP Server

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

Low Risk

Why list_available_personal_info needs a policy

This tool retrieves and enumerates personal data but does not create, modify, delete, or execute any actions. It is a pure read operation constrained by 'current permissions'.

From the tool's definition Tool name 'list_available_personal_info' and description 'List all available personal information' explicitly indicates a retrieval/listing operation with no modification or deletion capability.

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

How to control list_available_personal_info

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

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

list_available_personal_info 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 Personal Context 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.

Related tools and policies

Go deeper

Questions about list_available_personal_info

What does the list_available_personal_info tool do? +

List all available personal information within current permissions. It is categorised as a Read tool in the Personal Context MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_available_personal_info? +

Register the Personal Context MCP Server MCP server in PolicyLayer and add a rule for list_available_personal_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 Personal Context MCP Server. Nothing to install.

What risk level is list_available_personal_info? +

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

Can I rate-limit list_available_personal_info? +

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

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

list_available_personal_info is provided by the Personal Context MCP Server MCP server (matipojo/personal-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Personal Context MCP Server tool call.

Start from Personal Context MCP Server, 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.

9 Personal Context MCP Server 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.