New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_glp_scope_group

Update an RBAC scope group by ID.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/update-glp-scope-group.md

What update_glp_scope_group does on API-Central

AI agents use update_glp_scope_group to create or update resources in API-Central, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.

Why update_glp_scope_group is rated Medium

This tool modifies Role-Based Access Control (RBAC) scope group settings, which affects user permissions and network access policies. While reversible (Write rather than Destructive), the modification of security-critical RBAC configurations poses significant risk if an AI agent misconfigures scope groups, potentially granting or restricting inappropriate access to network resources.

From the tool's definition Tool name contains 'update' and description states 'Update an RBAC scope group by ID', which modifies access control configuration reversibly.

Questions about update_glp_scope_group

What does the update_glp_scope_group tool do? +

Update an RBAC scope group by ID. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_glp_scope_group? +

Register the API-Central MCP server in PolicyLayer and add a rule for update_glp_scope_group: 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 API-Central. Nothing to install.

What risk level is update_glp_scope_group? +

update_glp_scope_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_glp_scope_group? +

Yes. Add a rate_limit block to the update_glp_scope_group 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.

How do I block update_glp_scope_group completely? +

Set action: deny in the PolicyLayer policy for update_glp_scope_group. 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.

What MCP server provides update_glp_scope_group? +

update_glp_scope_group is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on API-Central, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of API-Central's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.