AI agents use create_personage to create or update resources in Yanifend — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yanifend environment.
This tool creates new resources (questionary, personage character, and API key) which are reversible via deletion operations (like delete_question visible on the same server). The creation of an embeddable API key represents a system-level change but remains within Write category since it doesn't irreversibly destroy data, execute arbitrary code, or move money.
From the tool's definition Tool description states 'Create a NEW personage — a fresh questionary plus its own character and an embeddable API key.' The verb 'Create' and the use of 'NEW' indicates this tool creates new data structures (questionary, character, API key) that persist in…
Attacks that exploit this kind of access
Create a NEW personage — a fresh questionary plus its own character and an embeddable API key. This is how you. It is categorised as a Write tool in the Yanifend MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yanifend MCP server in PolicyLayer and add a rule for create_personage: 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 Yanifend. Nothing to install.
create_personage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_personage 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 create_personage. 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.
create_personage is provided by the Yanifend MCP server (skippedaga/yanifend-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 →