http_put
A write tool on the Mcp Nettools MCP server.
This record as markdown: /tools/aaronckj-mcp-nettools/http-put.md
What http_put does on Mcp Nettools
AI agents use http_put to create or update resources in Mcp Nettools, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Nettools environment.
Why http_put is rated Medium
HTTP PUT semantics are to create or overwrite a resource, which maps to Write. However, the description is empty, so we cannot confirm what target or payload is involved. Confidence is reduced accordingly. It could also be Execute if it triggers side effects, but Write is the most likely baseline classification for PUT.
From the tool's definition Tool name 'http_put' — HTTP PUT is a standard method for creating or replacing a resource at a given URL.
Attacks that exploit this kind of access
The rule that runs http_put safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For http_put, this is the rule to start with:
http_put 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 Mcp Nettools, apply this rule, and every http_put call is checked against it from then on.
Questions about http_put
http_put is a write tool on the Mcp Nettools MCP server. It is categorised as a Write tool in the Mcp Nettools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for http_put: 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 Nettools. Nothing to install.
http_put 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_put 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_put. 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_put is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue