update_file_category · Buildium MCP Server MCP

WHAT IT DOES

What update_file_category does on Buildium MCP Server

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

WHY IT NEEDS A POLICY

Why update_file_category needs a policy

This tool modifies metadata (file categorization) within a property management system but does not delete, execute code, or commit financial transactions. Updates are typically reversible through subsequent corrections. The impact is scoped to organizational data structures rather than tenant records or financial transactions, warranting 'Write' classification.

From the tool's definition Tool name contains 'update' and description states 'Update a file category', indicating modification of existing data. The action is reversible and creates no permanent loss.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_file_category Rate-limited

update_file_category 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_file_category": {
      "limits": [
        {
          "counter": "update_file_category_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 Buildium MCP Server, so you can run agents against it safely.

FAQ

Questions about update_file_category

What does the update_file_category tool do? +

Update a file category. It is categorised as a Write tool in the Buildium 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_file_category? +

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

What risk level is update_file_category? +

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

Can I rate-limit update_file_category? +

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

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

update_file_category is provided by the Buildium MCP Server MCP server (luthersystems/mcp-server-buildium). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.