list_personas

List selectable personas (built-ins plus your custom personas).

SERVERPersonhood SOURCEhttps://api.givepersonhood.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-givepersonhood-personhood/list-personas.md

WHAT IT DOES

What list_personas does on Personhood

AI agents call list_personas to retrieve information from Personhood without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_personas is rated Low

Even though list_personas only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_personas safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Personhood, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_personas, this is the rule to start with:

list_personas Allowed

list_personas is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_personas": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Personhood, apply this rule, and every list_personas call is checked against it from then on.

FAQ

Questions about list_personas

What does the list_personas tool do? +

List selectable personas (built-ins plus your custom personas). It is categorised as a Read tool in the Personhood MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_personas? +

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

What risk level is list_personas? +

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

Can I rate-limit list_personas? +

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

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

list_personas is provided by the Personhood MCP server (https://api.givepersonhood.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Personhood, and thousands of servers like it.

This server

All 3 Personhood tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →