Get FluentCommunity branding settings (logo, favicon, custom CSS)
AI agents call fc_get_branding to retrieve information from FluentCommunity Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only branding configuration settings from the FluentCommunity plugin. It has no side effects, does not modify or delete data, and does not execute external operations. The 'Get' verb and the nature of branding settings (display parameters) confirm this is a simple data retrieval operation with minimal risk.
From the tool's definition Tool name 'fc_get_branding' and description 'Get FluentCommunity branding settings (logo, favicon, custom CSS)' indicate retrieval of configuration data with no modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get FluentCommunity branding settings (logo, favicon, custom CSS). It is categorised as a Read tool in the FluentCommunity Manager MCP Server, which means it retrieves data without modifying state.
Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for fc_get_branding: 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.
fc_get_branding is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fc_get_branding 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.
Set action: deny in the PolicyLayer policy for fc_get_branding. 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.
fc_get_branding 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →