New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

curl_request

Execute a curl request to an external HTTP API.

SERVERMCP Filesystem Server SOURCEa-niranjan/mcp-filesystem
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a-niranjan-mcp-filesystem/curl-request.md

What curl_request does on MCP Filesystem Server

AI agents invoke curl_request to trigger actions in MCP Filesystem 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.

Why curl_request is rated High

This tool executes external HTTP requests, which can trigger side effects on remote systems depending on the request parameters (POST, PUT, DELETE operations). While it does not modify local filesystem directly, it performs external operations whose consequences depend entirely on the arguments provided—making it an Execute category risk.

From the tool's definition Tool name 'curl_request' combined with description 'Execute a curl request to an external HTTP API' indicates execution of arbitrary HTTP operations to external systems.

Questions about curl_request

What does the curl_request tool do? +

Execute a curl request to an external HTTP API. It is categorised as a Execute tool in the MCP Filesystem Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on curl_request? +

Register the MCP Filesystem Server MCP server in PolicyLayer and add a rule for curl_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 MCP Filesystem Server. Nothing to install.

What risk level is curl_request? +

curl_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit curl_request? +

Yes. Add a rate_limit block to the curl_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.

How do I block curl_request completely? +

Set action: deny in the PolicyLayer policy for curl_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.

What MCP server provides curl_request? +

curl_request is provided by the MCP Filesystem Server MCP server (a-niranjan/mcp-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on MCP Filesystem Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MCP Filesystem Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.