AI agents use write_record_with_fields to create or update resources in UOFastMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UOFastMCP environment.
This tool creates or modifies data reversibly within database records. It is a Write operation rather than Destructive because it updates specific fields without deleting records or data, allowing potential rollback through subsequent writes.
From the tool's definition Tool name 'write_record_with_fields' and description 'Write specific DICT fields to a record' and 'updating only specific fields' explicitly indicate data modification.
Attacks that exploit this kind of access
Write specific DICT fields to a record using field names. This allows updating only specific fields without affecting other fields in the record. It is categorised as a Write tool in the UOFastMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UOFast MCP server in PolicyLayer and add a rule for write_record_with_fields: 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 UOFastMCP. Nothing to install.
write_record_with_fields 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 write_record_with_fields 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 write_record_with_fields. 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.
write_record_with_fields is provided by the UOFast MCP server (rokipark/uofastmcp). 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 →