New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

record_feedback

Record explicit user interaction history for a content item. Feedback actions: -

SERVER4da SOURCE4DA-Systems/4da-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/4da-mcp-server/record-feedback.md

What record_feedback does on 4da

AI agents call record_feedback to retrieve information from 4da without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why record_feedback is rated Low

Even though record_feedback only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about record_feedback

What does the record_feedback tool do? +

Record explicit user interaction history for a content item. Feedback actions: -. It is categorised as a Read tool in the 4da MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on record_feedback? +

Register the 4da MCP server in PolicyLayer and add a rule for record_feedback: 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 4da. Nothing to install.

What risk level is record_feedback? +

record_feedback is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit record_feedback? +

Yes. Add a rate_limit block to the record_feedback 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.

How do I block record_feedback completely? +

Set action: deny in the PolicyLayer policy for record_feedback. 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.

What MCP server provides record_feedback? +

record_feedback is provided by the 4da MCP server (4DA-Systems/4da-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 4da, and thousands of servers like it.

This server

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 4da's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.