get_account

Returns the user's account profile: plan and features, personal display limits and remaining quota, accessible display count, organization memberships and points balance. Use for subscription, quota and membership questions. Not for listing displays (use list_displays). Requires content scope.

SERVERagentView SOURCEhttps://agentview.de/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/de-agentview-agentview-mcp/get-account.md

WHAT IT DOES

What get_account does on agentView

AI agents call get_account to retrieve information from agentView without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`access_token`	string	—	Optional bearer token; prefer session_request_id.

Parameters from the server's own tool schema.

RISK

Why get_account is rated Low

Even though get_account only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHandles credentials or secrets (access_token)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_account safely

PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, 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 Allowed

get_account is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_account": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect agentView, apply this rule, and every get_account call is checked against it from then on.

FAQ

Questions about get_account

What does the get_account tool do? +

What parameters does get_account accept? +

get_account accepts 1 parameter: access_token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_account? +

Register the agentView 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 agentView. Nothing to install.

What risk level is get_account? +

get_account is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_account? +

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.

How do I block get_account completely? +

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.

What MCP server provides get_account? +

get_account is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on agentView, and thousands of servers like it.

This server

All 57 agentView tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →