fc_update_portal_settings · FluentCommunity Manager MCP

WHAT IT DOES

What fc_update_portal_settings does on FluentCommunity Manager

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

WHY IT NEEDS A POLICY

Why fc_update_portal_settings needs a policy

This tool modifies portal settings reversibly—changes can be undone by updating them again. It does not delete data (Destructive), execute arbitrary code (Execute), create financial obligations (Financial), or move money. While it's a write operation affecting site appearance and user experience, the changes are non-destructive and scoped to UI/display configuration.

From the tool's definition Tool name 'fc_update_portal_settings' and description 'Update FluentCommunity portal display settings (layout, sidebar, features)' indicate modification of configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fc_update_portal_settings Rate-limited

fc_update_portal_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": {
    "fc_update_portal_settings": {
      "limits": [
        {
          "counter": "fc_update_portal_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 FluentCommunity Manager, so you can run agents against it safely.

FAQ

Questions about fc_update_portal_settings

What does the fc_update_portal_settings tool do? +

Update FluentCommunity portal display settings (layout, sidebar, features). It is categorised as a Write tool in the FluentCommunity Manager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fc_update_portal_settings? +

Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for fc_update_portal_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 FluentCommunity Manager. Nothing to install.

What risk level is fc_update_portal_settings? +

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

Can I rate-limit fc_update_portal_settings? +

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

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

fc_update_portal_settings is provided by the FluentCommunity Manager MCP server (wplaunchify/fluent-community-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.