Add a user to a FluentCommunity space
AI agents use fc_add_space_member 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.
Adding a member to a space is a write operation that creates a new association or modifies membership state. While this modifies data, it is reversible (members can be removed), so it does not qualify as Destructive.
From the tool's definition Tool name 'fc_add_space_member' and description 'Add a user to a FluentCommunity space' indicates creation/modification of membership data. This is a reversible write operation that adds a user relationship to a space.
Attacks that exploit this kind of access
Add a user to a FluentCommunity space. 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.
Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for fc_add_space_member: 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_add_space_member is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fc_add_space_member 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_add_space_member. 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_add_space_member 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 →