Makes an authenticated API call. Handles login automatically — if the token is expired it re-logins transparently.
AI agents invoke request to trigger actions in Rest Api. 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 executes authenticated REST API calls to arbitrary endpoints. Depending on the endpoint called, effects could range from Read to Destructive or Financial. Since the tool is a general-purpose HTTP executor whose impact depends entirely on the arguments passed (method, endpoint, payload), and it spans all possible categories, the most severe applicable category is Execute.
From the tool's definition 'Makes an authenticated API call' and 'Handles login automatically' — executes arbitrary HTTP requests against external APIs with full authentication
Documented attack patterns abuse exactly the kind of access request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rest Api, and nothing reaches the server without passing your rules. This is the rule we recommend for request:
{
"version": "1",
"default": "deny",
"tools": {
"request": {
"limits": [
{
"counter": "request_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}request 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.
Makes an authenticated API call. Handles login automatically — if the token is expired it re-logins transparently. It is categorised as a Execute tool in the Rest Api MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rest Api MCP server in PolicyLayer and add a rule for request: 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 Rest Api. Nothing to install.
request 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 request 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 request. 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.
request is provided by the Rest Api MCP server (muhammed-abdelghany/rest_api_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rest Api, 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.
5 Rest Api tools catalogued and risk-classified — across an index of 43,000+ MCP servers.