Get account information including tier, limits, and usage stats.
AI agents call get_account to retrieve information from Lobstermail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only account metadata (tier, limits, usage statistics). It does not create, modify, delete, or execute any operations. The information retrieved could inform an agent's behavior but contains no sensitive secrets or financial data that would warrant higher severity. Misuse would be limited to gathering account details without actionable consequences.
From the tool's definition Tool description states 'Get account information including tier, limits, and usage stats' — a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get account information including tier, limits, and usage stats. It is categorised as a Read tool in the Lobstermail MCP Server, which means it retrieves data without modifying state.
Register the Lobstermail MCP server in PolicyLayer and add a rule for get_account: 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 Lobstermail. Nothing to install.
get_account 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_account 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_account. 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_account is provided by the Lobstermail MCP server (lobster-kit/mcp-server-lobstermail). 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 →