AI agents call list_integration_keys to retrieve information from Yanifend 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 integration/credential information for personages without modifying, executing code, deleting, or moving money. The public API keys and widget URLs are configuration data meant to be read and shared for embedding purposes. While the returned credentials are sensitive, the tool itself performs only a read operation.
From the tool's definition Tool name is 'list_integration_keys' and description states 'Get the embed credentials' — a retrieval operation with no modification or deletion. Returns read-only data (id, name, public API key, widget script URL).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get the embed credentials for every personage: id, name, public API key, widget script URL and a ready-to-paste. It is categorised as a Read tool in the Yanifend MCP Server, which means it retrieves data without modifying state.
Register the Yanifend MCP server in PolicyLayer and add a rule for list_integration_keys: 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.
list_integration_keys 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 list_integration_keys 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 list_integration_keys. 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.
list_integration_keys 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 →