check_social_accounts
List all connected and disconnected social accounts for the active brand. Lists default short; pass detail=medium/full for more fields. Run before posting to confirm platform availability.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/check-social-accounts.md
What check_social_accounts does on Postking Mcp
AI agents call check_social_accounts to retrieve information from Postking Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_social_accounts is rated Low
This tool retrieves and queries the status of social media accounts associated with a brand. It performs no write operations, does not delete data, does not execute external actions, and does not involve financial transactions. The optional detail parameter only controls verbosity of the response, not the action performed. It is purely informational, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'check_social_accounts' and description 'List all connected and disconnected social accounts' indicate a retrieval operation with no modification or side effects. Verbs used are 'list' and passive inspection.
Attacks that exploit this kind of access
The rule that runs check_social_accounts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_social_accounts, this is the rule to start with:
check_social_accounts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every check_social_accounts call is checked against it from then on.
Questions about check_social_accounts
List all connected and disconnected social accounts for the active brand. Lists default short; pass detail=medium/full for more fields. Run before posting to confirm platform availability. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.
Register the Postking MCP server in PolicyLayer and add a rule for check_social_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 Postking Mcp. Nothing to install.
check_social_accounts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_social_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.
Set action: deny in the PolicyLayer policy for check_social_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.
check_social_accounts is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
This server
Across the catalogue