AI agents use jsr_update_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 creates or modifies data reversibly (updating member roles), fitting the Write category. It is high severity because unauthorized role changes could grant malicious actors access to sensitive operations or revoke legitimate access, affecting package governance and security.
From the tool's definition Tool description states 'Update scope member roles' — a modification operation that changes member permissions/access levels within a scope. Requires 'scope admin' authentication, indicating privileged access.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Update scope member roles (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_update_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_update_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_update_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_update_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_update_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 →