Create, delete, or update applications within application groups in a specified policy. Supported types: bat, cpl, exe, msc, msi, ps1, reg, rpsc, rpss, unex, wsh. To update an existing application, first delete it then create the updated version.
AI agents use create_policy_application to create or update resources in BeyondTrust EPM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BeyondTrust EPM MCP Server environment.
This is primarily a Write operation that modifies policy configurations by creating or updating application entries. However, the ability to manage executable and script types (exe, ps1, bat, msi) within privilege management policies creates risk of privilege escalation or malware distribution if misused.
From the tool's definition Tool performs create, delete, or update operations on applications within policy application groups. Description explicitly states 'Create, delete, or update applications' and supports executable/script types (exe, ps1, bat, msi, msc).
Attacks that exploit this kind of access
Create, delete, or update applications within application groups in a specified policy. Supported types: bat, cpl, exe, msc, msi, ps1, reg, rpsc, rpss, unex, wsh. To update an existing application, first delete it then create the updated version. It is categorised as a Write tool in the BeyondTrust EPM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BeyondTrust EPM MCP Server MCP server in PolicyLayer and add a rule for create_policy_application: 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 BeyondTrust EPM MCP Server. Nothing to install.
create_policy_application 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_policy_application 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_policy_application. 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_policy_application is provided by the BeyondTrust EPM MCP Server MCP server (wesharris222/btepmmcp). 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 →