list_accounts

List all connected social media accounts on PostEverywhere. Returns account IDs, platform names, usernames, and health status (whether each account can currently post). Use this to see which platforms are available before creating a post.

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

What list_accounts does on Posteverywhere

AI agents call list_accounts 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 list_accounts needs a policy

This tool retrieves and queries existing account metadata without creating, modifying, or deleting any data. It is purely informational and serves to enumerate available accounts before other operations. The blast radius of misuse is minimal—an agent could enumerate accounts but cannot take action with them without using other tools. This is a classic Read category operation.

From the tool's definition Tool description explicitly states 'List all connected social media accounts' and 'Returns account IDs, platform names, usernames, and health status'.

Questions about list_accounts

What does the list_accounts tool do? +

List all connected social media accounts on PostEverywhere. Returns account IDs, platform names, usernames, and health status (whether each account can currently post). Use this to see which platforms are available before creating a post. 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 list_accounts? +

Register the Posteverywhere MCP server in PolicyLayer and add a rule for list_accounts: 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 list_accounts? +

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

Can I rate-limit list_accounts? +

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

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

list_accounts 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.