Retrieve multiple categories of personal information in a single request. Retrieve personal information based on category and current permissions, you can get a wide range of information, personal, pets, family, friends, work, etc and even more. You must list once all the categories with the list...
AI agents call batch_get_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.
This tool retrieves personal information without modifying or deleting it, making it a Read operation. However, severity is high rather than low because: (1) the tool accesses broad categories of sensitive personal information (personal, family, friends, contacts, etc.), (2) the server description indicates the data is sensitive enough to warrant AES-256 encryption and optional OTP authentication, and (3)…
From the tool's definition Tool description explicitly states 'Retrieve multiple categories of personal information' and 'Retrieve personal information based on category'.
Documented attack patterns abuse exactly the kind of access batch_get_personal_info gives an agent:
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 batch_get_personal_info:
{
"version": "1",
"default": "deny",
"tools": {
"batch_get_personal_info": {}
}
}batch_get_personal_info 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.
Retrieve multiple categories of personal information in a single request. Retrieve personal information based on category and current permissions, you can get a wide range of information, personal, pets, family, friends, work, etc and even more. You must list once all the categories with the list_available_personal_info tool before using this tool to understand what you can get. It is categorised as a Read tool in the Personal Context MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Personal Context MCP Server MCP server in PolicyLayer and add a rule for batch_get_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.
batch_get_personal_info 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 batch_get_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.
Set action: deny in the PolicyLayer policy for batch_get_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.
batch_get_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.
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.