특정 페르소나의 설문 히스토리를 조회합니다.
AI agents call get_persona_survey_history_tool to retrieve information from Persona 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 retrieves historical survey data associated with a persona. It performs a read-only operation with no side effects, data modifications, or irreversible actions. The blast radius of misuse is minimal—an agent could access persona survey histories it shouldn't, but no data would be altered or destroyed.
From the tool's definition Tool name contains 'get_' and description states '조회합니다' (retrieves/queries in Korean). The function retrieves survey history for a specific persona without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
특정 페르소나의 설문 히스토리를 조회합니다. It is categorised as a Read tool in the Persona MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Persona MCP Server MCP server in PolicyLayer and add a rule for get_persona_survey_history_tool: 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 Persona MCP Server. Nothing to install.
get_persona_survey_history_tool 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_persona_survey_history_tool 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_persona_survey_history_tool. 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_persona_survey_history_tool is provided by the Persona MCP Server MCP server (seonaru/persona-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 →