Low Risk

persona_count

Number of personas to interview (default: 10)

Part of the Signal Relay server.

persona_count is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE SIGNAL RELAY →

Free to start. No card required.

AI agents call persona_count to retrieve information from Signal Relay without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though persona_count only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Signal Relay policy for all 30 tools.

Get this rule live on your own Signal Relay server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SIGNAL RELAY →

View all 30 tools →

These attack patterns abuse exactly the kind of access persona_count gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so persona_count only ever does what you allow.

SECURE SIGNAL RELAY →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the persona_count tool do? +

Number of personas to interview (default: 10). It is categorised as a Read tool in the Signal Relay MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on persona_count? +

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

What risk level is persona_count? +

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

Can I rate-limit persona_count? +

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

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

persona_count is provided by the Signal Relay MCP server (SocioLogicAI/signal-relay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Signal Relay tool call.

Deterministic rules across all 30 Signal Relay tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.