get_plugin_scaffold_template · Backstage MCP Server MCP

WHAT IT DOES

What get_plugin_scaffold_template does on Backstage MCP Server

AI agents use get_plugin_scaffold_template to create or update resources in Backstage MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Backstage MCP Server environment.

WHY IT NEEDS A POLICY

Why get_plugin_scaffold_template needs a policy

This tool generates (creates) scaffold template code/files based on configuration. It produces new content/artifacts, placing it in the Write category. It is not purely reading existing data, but creating new structured output. Severity is medium as misuse could generate malformed or malicious plugin scaffolding, though effects are likely reversible.

From the tool's definition "Generate a plugin scaffold template with specified configuration"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

get_plugin_scaffold_template Rate-limited

get_plugin_scaffold_template 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_plugin_scaffold_template": {
      "limits": [
        {
          "counter": "get_plugin_scaffold_template_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Backstage MCP Server, so you can run agents against it safely.

FAQ

Questions about get_plugin_scaffold_template

What does the get_plugin_scaffold_template tool do? +

Generate a plugin scaffold template with specified configuration. It is categorised as a Write tool in the Backstage MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on get_plugin_scaffold_template? +

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

What risk level is get_plugin_scaffold_template? +

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

Can I rate-limit get_plugin_scaffold_template? +

Yes. Add a rate_limit block to the get_plugin_scaffold_template 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 get_plugin_scaffold_template completely? +

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

get_plugin_scaffold_template is provided by the Backstage MCP Server MCP server (pawelwaj/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.