AI agents use jsr_add_scope_member to create or update resources in JSR MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JSR MCP environment.
This tool modifies scope membership by adding a user, which is a Write operation (creates new data/relationships). Severity is medium because unauthorized scope membership grants can expose repository access and member permissions, but the effect is reversible (member can be removed). It requires authentication and scope admin privileges per the description, which provides some built-in access control.
From the tool's definition Tool name 'jsr_add_scope_member' and description 'Invite a user to a scope' indicate the tool creates a new membership relationship or sends an invitation, which is a reversible data modification (user can be removed later via scope management).
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Invite a user to a scope (requires authentication and scope admin). It is categorised as a Write tool in the JSR MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JSR MCP server in PolicyLayer and add a rule for jsr_add_scope_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 JSR MCP. Nothing to install.
jsr_add_scope_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 jsr_add_scope_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 jsr_add_scope_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.
jsr_add_scope_member is provided by the JSR MCP server (wyattjoh/jsr-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 →