getAccountDetails

SERVERSocial Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) SOURCEhttps://mcp.xpoz.ai/mcp

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-xpoz-social-insights/getaccountdetails.md

WHAT IT DOES

What getAccountDetails does on Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ)

AI agents call getAccountDetails to retrieve information from Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) 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
`feedback`	string	—	Optional. Any free-form feedback you want to share — about this tool, other tools, the platform overall, or anything else. Feedback does NOT have to be about th
`_requestId`	string	—

Parameters from the server's own tool schema.

RISK

Why getAccountDetails is rated Low

This is a read-only query that retrieves and returns account information without side effects. It does not create, modify, delete, or execute any operations. The data returned (plan name, billing period, subscription credits) are informational only. While billing-related, it merely reads billing state rather than moving money or committing financial obligations, so Financial category does not apply.

From the tool's definition Tool name 'getAccountDetails' and description explicitly state it 'Get[s] authenticated user's account details' returning 'plan/billing/usage object'. No modification, deletion, or execution occurs—only retrieval of existing account metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getAccountDetails safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getAccountDetails, this is the rule to start with:

getAccountDetails Allowed

getAccountDetails 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": {
    "getAccountDetails": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), apply this rule, and every getAccountDetails call is checked against it from then on.

FAQ

Questions about getAccountDetails

What does the getAccountDetails tool do? +

Get authenticated user's account details: plan (name, features), billing (period, next renewal date; null for Free plan), and usage (subscription credits remaining, extra credits remaining, extra tracked items). Required: authentication. Returns: nested plan/billing/usage object. It is categorised as a Read tool in the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP Server, which means it retrieves data without modifying state.

What parameters does getAccountDetails accept? +

getAccountDetails accepts 2 parameters: feedback, _requestId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getAccountDetails? +

Register the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server in PolicyLayer and add a rule for getAccountDetails: 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 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ). Nothing to install.

What risk level is getAccountDetails? +

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

Can I rate-limit getAccountDetails? +

Yes. Add a rate_limit block to the getAccountDetails 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 getAccountDetails completely? +

Set action: deny in the PolicyLayer policy for getAccountDetails. 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 getAccountDetails? +

getAccountDetails is provided by the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server (https://mcp.xpoz.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), and thousands of servers like it.

This server

All 52 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) tools →

Across the catalogue

The MCP Attack Database →

Guides

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