create_project_from_template
AI agents use create_project_from_template to create or update resources in PensionPro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PensionPro environment.
The verb 'create' coupled with 'project' in a pension administration context suggests the tool generates and persists a new project entity, which is a reversible write operation. Without a description, confidence is moderately reduced, but the name pattern clearly indicates data creation rather than deletion, execution, or financial transaction.
From the tool's definition Tool name 'create_project_from_template' indicates creation of a new project resource from a template. Description is empty, limiting specificity.
Attacks that exploit this kind of access
create_project_from_template. It is categorised as a Write tool in the PensionPro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PensionPro MCP server in PolicyLayer and add a rule for create_project_from_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 PensionPro. Nothing to install.
create_project_from_template 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_project_from_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.
Set action: deny in the PolicyLayer policy for create_project_from_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.
create_project_from_template is provided by the PensionPro MCP server (pypi:pension-pro-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 →