read_client_vault
AI agents call read_client_vault to retrieve information from KonQuest Meta Ads MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name unambiguously indicates a Read operation. Although the description is empty, reducing confidence slightly, the read_ prefix combined with a Meta Ads campaign management context and adjacent tools (which are clearly Write, Execute, or Destructive) suggests this retrieves client information from secure storage. No evidence of side effects, modifications, deletions, or financial transactions.
From the tool's definition Tool name 'read_client_vault' explicitly contains 'read', indicating a retrieval operation. No description provided, but the 'read_' prefix and 'vault' context (likely storing client credentials or sensitive data) strongly suggest data retrieval without…
Attacks that exploit this kind of access
read_client_vault. It is categorised as a Read tool in the KonQuest Meta Ads MCP MCP Server, which means it retrieves data without modifying state.
Register the KonQuest Meta Ads MCP server in PolicyLayer and add a rule for read_client_vault: 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 KonQuest Meta Ads MCP. Nothing to install.
read_client_vault 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 read_client_vault 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 read_client_vault. 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.
read_client_vault is provided by the KonQuest Meta Ads MCP server (brandu-mos/konquest-meta-ads-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 →