record_execution_feedback · RobotWS MCP Server MCP

WHAT IT DOES

What record_execution_feedback does on RobotWS MCP Server

AI agents use record_execution_feedback to create or update resources in RobotWS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RobotWS MCP Server environment.

WHY IT NEEDS A POLICY

Why record_execution_feedback needs a policy

The name implies recording or storing feedback about execution results, which is a Write operation. However, with no description available, confidence is low. It could potentially be Execute if it triggers some action, but Write is the most reasonable inference from the name alone.

From the tool's definition Tool name 'record_execution_feedback' suggests writing/storing feedback data, but the description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_execution_feedback Rate-limited

record_execution_feedback stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_execution_feedback": {
      "limits": [
        {
          "counter": "record_execution_feedback_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RobotWS MCP Server, so you can run agents against it safely.

FAQ

Questions about record_execution_feedback

What does the record_execution_feedback tool do? +

record_execution_feedback. It is categorised as a Write tool in the RobotWS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_execution_feedback? +

Register the RobotWS MCP Server MCP server in PolicyLayer and add a rule for record_execution_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 RobotWS MCP Server. Nothing to install.

What risk level is record_execution_feedback? +

record_execution_feedback is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_execution_feedback? +

Yes. Add a rate_limit block to the record_execution_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_execution_feedback completely? +

Set action: deny in the PolicyLayer policy for record_execution_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_execution_feedback? +

record_execution_feedback is provided by the RobotWS MCP Server MCP server (stella555359/robotws_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

record_execution_feedback is one line of RobotWS MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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