Make a PUT HTTP request
AI agents use put to create or update resources in API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API MCP Server environment.
PUT requests modify existing resources, making this a Write operation rather than Read (no retrieval-only) or Execute (no arbitrary code execution). The severity is medium because unintended modifications to notes could occur, but the impact is reversible via subsequent PUT requests or the 'delete' tool. Confidence is high because PUT's semantics as an update operation are well-established in HTTP standards.
From the tool's definition Tool description states 'Make a PUT HTTP request' which performs updates/modifications. In HTTP semantics, PUT is used to update or replace resources.
Attacks that exploit this kind of access
Make a PUT HTTP request. It is categorised as a Write tool in the API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the API MCP Server MCP server in PolicyLayer and add a rule for 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 API MCP Server. Nothing to install.
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 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 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.
put is provided by the API MCP Server MCP server (vilasone455/api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →