update_followup_settings · Rentalot MCP Server MCP

WHAT IT DOES

What update_followup_settings does on Rentalot MCP Server

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

WHY IT NEEDS A POLICY

Why update_followup_settings needs a policy

This tool creates or modifies data (follow-up automation settings) without deleting or overwriting irreversibly. It is a Write operation that could affect business automation workflows if misconfigured by an agent, hence medium severity. The Pro tier requirement indicates this is a protected feature, suggesting organizational awareness of its importance.

From the tool's definition Tool description explicitly states "Write operation" and specifies it "update[s] follow-up automation settings." This modifies configuration data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_followup_settings Rate-limited

update_followup_settings 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_followup_settings": {
      "limits": [
        {
          "counter": "update_followup_settings_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 Rentalot MCP Server, so you can run agents against it safely.

FAQ

Questions about update_followup_settings

What does the update_followup_settings tool do? +

Use to update follow-up automation settings. Only include fields you want to change. Write operation — requires Pro tier or higher. It is categorised as a Write tool in the Rentalot 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 update_followup_settings? +

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

What risk level is update_followup_settings? +

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

Can I rate-limit update_followup_settings? +

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

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

update_followup_settings is provided by the Rentalot MCP Server MCP server (rentalot-ai/rentalot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.