sync_space
AI agents use sync_space to create or update resources in Better Confluence — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Better Confluence environment.
A 'sync_space' tool on a server designed to sync Confluence spaces likely reads from Confluence and writes to local files (or vice versa). Given the server context of syncing spaces for editing, this could involve writing/overwriting local files or updating Confluence content. The most severe plausible category is Write (or potentially Destructive if it overwrites).
From the tool's definition Tool name 'sync_space' and server description mentions 'Syncs Confluence spaces to local files for efficient editing'; description is empty, reducing confidence.
Attacks that exploit this kind of access
sync_space. It is categorised as a Write tool in the Better Confluence MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Better Confluence MCP server in PolicyLayer and add a rule for sync_space: 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 Better Confluence. Nothing to install.
sync_space 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 sync_space 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 sync_space. 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.
sync_space is provided by the Better Confluence MCP server (twinity1/better-confluence-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 →