get_account

Get detailed information about a specific connected social media account on PostEverywhere. Returns the account platform, username, health status, and whether it can currently post. Use this to check the status of a single account by its ID.

Server Posteverywhere posteverywhere/mcp
Category Read
Risk class Low
Parameters 00 required

What get_account does on Posteverywhere

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

Why get_account needs a policy

This is a read-only query operation that retrieves metadata about a connected social media account. It has no capacity to modify data, execute actions, delete resources, or commit financial transactions. The blast radius is minimal—account information disclosure is a data privacy concern but not an operational security risk in the context of MCP tool misuse.

From the tool's definition Tool retrieves account information (platform, username, health status, posting capability) with no modification or side effects. Description explicitly states 'Get detailed information' and 'check the status'.

Questions about get_account

What does the get_account tool do? +

Get detailed information about a specific connected social media account on PostEverywhere. Returns the account platform, username, health status, and whether it can currently post. Use this to check the status of a single account by its ID. It is categorised as a Read tool in the Posteverywhere MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_account? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.