create_glp_scope_group
A write tool on the API-Central MCP server.
This record as markdown: /tools/secure-ssid-centralmcp/create-glp-scope-group.md
What create_glp_scope_group does on API-Central
AI agents use create_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 create_glp_scope_group is rated Medium
The 'create' verb and GreenLake Platform context suggest this tool creates a new scope group configuration, which modifies system state reversibly. Without a description, confidence is moderate. Severity is medium because misconfiguration of GreenLake scope groups in a network operations context could affect access controls or resource organization, but is typically reversible.
From the tool's definition Tool name 'create_glp_scope_group' indicates creation of a GreenLake Platform scope group. Sibling tools include 'add_glp_scope_group_scopes' and other resource creation/modification operations. Description is empty, reducing confidence.
Attacks that exploit this kind of access
The rule that runs create_glp_scope_group safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_glp_scope_group, this is the rule to start with:
create_glp_scope_group stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every create_glp_scope_group call is checked against it from then on.
Questions about create_glp_scope_group
create_glp_scope_group is a write tool on the API-Central MCP server. 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.
Register the API-Central MCP server in PolicyLayer and add a rule for create_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.
create_glp_scope_group 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
This server
Across the catalogue