Get current account info: plan tier, usage counts, and limits.
AI agents call vitrine_account_info to retrieve information from Vitrine MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account metadata without modifying, executing operations, or causing financial transactions. The 'Get' verb and read-only nature clearly indicate a Read category classification. Severity is low since account information disclosure has limited blast radius in a product viewer platform context.
From the tool's definition Tool description states 'Get current account info' which is a retrieval operation with no side effects. Returns plan tier, usage counts, and limits—all informational data.
Attacks that exploit this kind of access
Get current account info: plan tier, usage counts, and limits. It is categorised as a Read tool in the Vitrine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vitrine MCP Server MCP server in PolicyLayer and add a rule for vitrine_account_info: 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 Vitrine MCP Server. Nothing to install.
vitrine_account_info 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 vitrine_account_info 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 vitrine_account_info. 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.
vitrine_account_info is provided by the Vitrine MCP Server MCP server (vitrine3d/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 →