get_psadt_template · Packager- MCP: Risk & Policy

WHAT IT DOES

What get_psadt_template does on Packager-MCP

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

WHY IT NEEDS A POLICY

Why get_psadt_template needs a policy

The tool generates PSADT deployment scripts and, when an output directory is provided, writes a complete package with toolkit files to the filesystem. This is a Write operation (creating new files/content). Misuse could result in malformed or malicious deployment scripts being packaged for enterprise software distribution, giving it medium severity.

From the tool's definition 'generates correct scripts', 'Returns a complete deployment script', 'creates a complete package with toolkit files' — the tool creates/writes files to disk when output_directory is specified, and generates script content

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

get_psadt_template Rate-limited

get_psadt_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_psadt_template": {
      "limits": [
        {
          "counter": "get_psadt_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 Packager-MCP, so you can run agents against it safely.

FAQ

Questions about get_psadt_template

What does the get_psadt_template tool do? +

ALWAYS use this tool to generate PSADT v4.1.7 deployment scripts. DO NOT write PSADT scripts manually - they will have incorrect function names. This tool generates correct scripts using Open-ADTSession and Close-ADTSession. Returns a complete deployment script with customization points. If output_directory is specified, creates a complete package with toolkit files. It is categorised as a Write tool in the Packager-MCP 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_psadt_template? +

Register the Packager- MCP server in PolicyLayer and add a rule for get_psadt_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 Packager-MCP. Nothing to install.

What risk level is get_psadt_template? +

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

Can I rate-limit get_psadt_template? +

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

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

get_psadt_template is provided by the Packager- MCP server (kkaminsk/packager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.