send the put request
AI agents use send-put-request to create or update resources in Api Testing — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Api Testing environment.
PUT requests typically update or modify existing data on a server. This is a reversible operation (Write category) rather than irreversible (Destructive). The severity is medium because misuse could modify arbitrary API resources depending on the target URL and payload, but the impact depends on what API endpoint is being called. Confidence is high because PUT semantics are well-established in HTTP standards.
From the tool's definition Tool name 'send-put-request' and description 'send the put request' indicate HTTP PUT method, which modifies existing resources. Server description states it 'Enables HTTP API testing (GET, POST, PUT, DELETE) via the Model Context Protocol'.
Attacks that exploit this kind of access
send the put request. It is categorised as a Write tool in the Api Testing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Api Testing MCP server in PolicyLayer and add a rule for send-put-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 Api Testing. Nothing to install.
send-put-request 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 send-put-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 send-put-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.
send-put-request is provided by the Api Testing MCP server (naveen-automation/mcp-server). 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 →