get_account
Get current user account information
This record as markdown: /tools/instantkom-mcp-server/get-account.md
What get_account does on instantKOM MCP Server
AI agents call get_account to retrieve information from instantKOM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_account is rated Low
This tool queries and retrieves existing account data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that returns information about the authenticated user's account. The severity is low because account metadata alone poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_account' combined with description 'Get current user account information' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_account, this is the rule to start with:
get_account is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every get_account call is checked against it from then on.
Questions about get_account
Get current user account information. It is categorised as a Read tool in the instantKOM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the instantKOM MCP Server 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 instantKOM MCP Server. 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 instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
This server
Across the catalogue