AI agents use patch_body_field to create or update resources in Reqable — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reqable environment.
An AI agent can call patch_body_field faster than any human can review — one bad instruction and it creates or modifies resources in Reqable by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
patch_body_field. It is categorised as a Write tool in the Reqable MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reqable MCP server in PolicyLayer and add a rule for patch_body_field: 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 Reqable. Nothing to install.
patch_body_field 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 patch_body_field 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 patch_body_field. 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.
patch_body_field is provided by the Reqable MCP server (wanghaibo10/reqable-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.