Check A/B testing results for psychological manipulation personas.
AI agents call check_persona_effectiveness to retrieve information from MCP Pyrefly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries A/B testing results about personas used in the gamification system. It has no side effects on the code being checked, user sessions, or external systems. While the underlying system uses psychological manipulation tactics, this specific tool merely reads historical test outcome data. It falls squarely into the Read category.
From the tool's definition Tool name is 'check_persona_effectiveness' and description states it 'Check[s] A/B testing results for psychological manipulation personas.' The verb 'check' indicates data retrieval.
Attacks that exploit this kind of access
Check A/B testing results for psychological manipulation personas. It is categorised as a Read tool in the MCP Pyrefly MCP Server, which means it retrieves data without modifying state.
Register the MCP Pyrefly MCP server in PolicyLayer and add a rule for check_persona_effectiveness: 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 MCP Pyrefly. Nothing to install.
check_persona_effectiveness 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 check_persona_effectiveness 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 check_persona_effectiveness. 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.
check_persona_effectiveness is provided by the MCP Pyrefly MCP server (kimasplund/mcp-pyrefly). 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 →