AI agents invoke refresh_seed_membership_site to trigger actions in SEED MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a deployment/refresh operation that modifies live infrastructure (the membership site) based on external state (GitHub branch content). While not immediately destructive, it triggers external processes whose side effects are not fully reversible and depend on what is in the GitHub branch.
From the tool's definition Tool name contains 'refresh' and description states 'Trigger a refresh of the SEED membership site from GitHub public branch' — this initiates an external operation (pulling/deploying from GitHub) whose effects depend on branch content and deployment logic.
Attacks that exploit this kind of access
Trigger a refresh of the SEED membership site from GitHub public branch. It is categorised as a Execute tool in the SEED MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SEED MCP server in PolicyLayer and add a rule for refresh_seed_membership_site: 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 SEED MCP. Nothing to install.
refresh_seed_membership_site is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the refresh_seed_membership_site 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 refresh_seed_membership_site. 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.
refresh_seed_membership_site is provided by the SEED MCP server (sancovp/seed-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 →