AI agents use http_post to create or update resources in MCP-RQuest — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-RQuest environment.
HTTP POST requests create or submit data to remote servers. Combined with the server's ability to bypass anti-bot measures and browser fingerprinting, this tool can write data to arbitrary web endpoints at scale. Severity is high because it can interact with any web service — submitting forms, creating accounts, posting content — potentially causing significant side effects depending on the target URL.
From the tool's definition Make an HTTP POST request to the specified URL
Documented attack patterns abuse exactly the kind of access http_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-RQuest, and nothing reaches the server without passing your rules. This is the rule we recommend for http_post:
{
"version": "1",
"default": "deny",
"tools": {
"http_post": {
"limits": [
{
"counter": "http_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}http_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.
Free to start. No card required.
Make an HTTP POST request to the specified URL. It is categorised as a Write tool in the MCP-RQuest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-RQuest MCP server in PolicyLayer and add a rule for http_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 MCP-RQuest. Nothing to install.
http_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 http_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 http_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.
http_post is provided by the MCP-RQuest MCP server (xxxbrian/mcp-rquest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 MCP-RQuest tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 MCP-RQuest tools catalogued and risk-classified — across an index of 42,500+ MCP servers.