bredgio_post
Dispatch a social post through one of the user's Bredgio agents (browsers). Returns a taskId — poll bredgio_task_status to see it go pending → running → completed (with the live post URL). The agent must be online. Use bredgio_list_agents first to pick an agentId.
This record as markdown: /tools/a3plus-mcp/bredgio-post.md
What bredgio_post does on A3plus
AI agents use bredgio_post to create or update resources in A3plus, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your A3plus environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
agentId | string | Yes | The Bredgio agent id (from bredgio_list_agents). |
content | string | Yes | The post text. |
platform | string | Yes | Target platform, e.g. "facebook". |
Parameters from the server's own tool schema.
Why bredgio_post is rated Medium
An AI agent can call bredgio_post faster than any human can review: one bad instruction and it creates or modifies resources in A3plus by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs bredgio_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A3plus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bredgio_post, this is the rule to start with:
bredgio_post stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect A3plus, apply this rule, and every bredgio_post call is checked against it from then on.
Questions about bredgio_post
Dispatch a social post through one of the user's Bredgio agents (browsers). Returns a taskId — poll bredgio_task_status to see it go pending → running → completed (with the live post URL). The agent must be online. Use bredgio_list_agents first to pick an agentId. It is categorised as a Write tool in the A3plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
bredgio_post accepts 3 parameters: agentId, content, platform. Required: agentId, content, platform. The full parameter table on this page comes from the server's own tool schema.
Register the A3plus MCP server in PolicyLayer and add a rule for bredgio_post: 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 A3plus. Nothing to install.
bredgio_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bredgio_post 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 bredgio_post. 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.
bredgio_post is provided by the A3plus MCP server (a3plus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A3plus, and thousands of servers like it.
This server
Across the catalogue