Verify that a PSADT script file uses only valid v4.1.7 function names. Use this after generating a package with get_psadt_template to ensure no invalid function names were introduced. Returns list of valid functions found, any invalid functions with suggested replacements, and parameter issues.
AI agents call verify_psadt_functions to retrieve information from Packager-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a validation/verification tool that performs static analysis on PSADT scripts. It reads and parses the script to check function names against a known list of valid v4.1.7 functions, then reports findings. No side effects occur: it does not execute the script, modify files, delete content, or trigger deployments.
From the tool's definition Tool verifies PSADT script files and returns a list of valid functions found, invalid functions, and parameter issues.
Attacks that exploit this kind of access
Verify that a PSADT script file uses only valid v4.1.7 function names. Use this after generating a package with get_psadt_template to ensure no invalid function names were introduced. Returns list of valid functions found, any invalid functions with suggested replacements, and parameter issues. It is categorised as a Read tool in the Packager-MCP MCP Server, which means it retrieves data without modifying state.
Register the Packager- MCP server in PolicyLayer and add a rule for verify_psadt_functions: 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.
verify_psadt_functions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the verify_psadt_functions 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 verify_psadt_functions. 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.
verify_psadt_functions 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.
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 →