Retrieve a single person record from WikiTree
AI agents call get_person to retrieve information from WikiTree MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns genealogical data from WikiTree without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with no destructive, financial, or execution capabilities. The low severity reflects minimal risk from misuse—retrieving a public genealogical record poses no significant threat.
From the tool's definition Tool name 'get_person' and description 'Retrieve a single person record from WikiTree' indicates a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Retrieve a single person record from WikiTree. It is categorised as a Read tool in the WikiTree MCP server MCP Server, which means it retrieves data without modifying state.
Register the WikiTree MCP server MCP server in PolicyLayer and add a rule for get_person: 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 WikiTree MCP server. Nothing to install.
get_person 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_person 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_person. 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_person is provided by the WikiTree MCP server MCP server (pewu/wikitree-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →