get_account

Get current user info including tier, usage, and limits

SERVERDeloc SOURCEdelocdev/deloc-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_account does on Deloc

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

RISK

Why get_account is rated Low

This tool retrieves account metadata without creating, modifying, or deleting resources. While it accesses user account information, the information returned (tier, usage, limits) is informational and carries minimal risk if accessed by an AI agent. No side effects or system state changes occur.

From the tool's definition Tool name 'get_account' and description 'Get current user info including tier, usage, and limits' indicate data retrieval only. The verb 'Get' and absence of modification language confirm read-only behavior.

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 Deloc, 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 Deloc, 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? +

Get current user info including tier, usage, and limits. It is categorised as a Read tool in the Deloc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_account? +

Register the Deloc 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 Deloc. 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 Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deloc, and thousands of servers like it.

This server

All 45 Deloc 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 →