Click the compose/new tweet button to open the tweet editor
AI agents invoke click-compose-button to trigger actions in MoltBrowser MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs a browser action (clicking a UI element) that triggers an external operation — opening the tweet composition editor on Twitter/X. It is an Execute-category action because it interacts with an external platform's UI. Severity is medium because while it only opens the editor (not submitting content), it initiates a workflow that could lead to unintended posts if combined with other tools.
From the tool's definition Click the compose/new tweet button to open the tweet editor
Documented attack patterns abuse exactly the kind of access click-compose-button gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MoltBrowser MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for click-compose-button:
{
"version": "1",
"default": "deny",
"tools": {
"click-compose-button": {
"limits": [
{
"counter": "click-compose-button_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} click-compose-button stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Click the compose/new tweet button to open the tweet editor. It is categorised as a Execute tool in the MoltBrowser MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MoltBrowser MCP Server MCP server in PolicyLayer and add a rule for click-compose-button: 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 MoltBrowser MCP Server. Nothing to install.
click-compose-button is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the click-compose-button 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 click-compose-button. 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.
click-compose-button is provided by the MoltBrowser MCP Server MCP server (joakim-sael/moltbrowser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MoltBrowser MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 MoltBrowser MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.