update_custom_record · Eduframe MCP: Risk & Policy

WHAT IT DOES

What update_custom_record does on Eduframe

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

WHY IT NEEDS A POLICY

Why update_custom_record needs a policy

This tool modifies existing data (a custom record) but does not irreversibly delete it, does not execute arbitrary code, and does not involve financial transactions. Updates are reversible through subsequent corrections.

From the tool's definition Tool name and description indicate it 'Update a custom record' — a reversible modification operation. The server description confirms it 'enabling...updating...leads' as a core function.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_custom_record Rate-limited

update_custom_record 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": {
    "update_custom_record": {
      "limits": [
        {
          "counter": "update_custom_record_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 Eduframe, so you can run agents against it safely.

FAQ

Questions about update_custom_record

What does the update_custom_record tool do? +

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

How do I enforce a policy on update_custom_record? +

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

What risk level is update_custom_record? +

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

Can I rate-limit update_custom_record? +

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

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

update_custom_record is provided by the Eduframe MCP server (martijnpieters/eduframe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.