# materializeTemplate

POST /v1/templates/{template_id}/materialize

Agent View of the PolicyLayer registry record for `materializeTemplate`. HTML page: https://policylayer.com/tools/vipcasso-mcp/materializetemplate

## Facts

- Tool: `materializeTemplate`
- Server: Vipcasso (`@vipcasso/mcp`) — https://policylayer.com/tools/vipcasso-mcp.md
- Install: `npx -y @vipcasso/mcp`
- Homepage: https://www.npmjs.com/package/@vipcasso/mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 5
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `body` | object | no |  |
| `files` | array | no |  |
| `query` | object | no |  |
| `fields` | object | no |  |
| `path_params` | object | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "materializeTemplate",
    "arguments": {}
  }
}
```

## Why materializeTemplate is rated Low

Even though materializeTemplate only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: Accepts file system path (files[].filename) · Accepts raw HTML/template content (body)

## Use case

AI agents call materializeTemplate to retrieve information from Vipcasso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Vipcasso:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "materializeTemplate": {}
  }
}
```

## Other tools on Vipcasso (232)

- `clearManagedAccountAiPrice` — Destructive — https://policylayer.com/tools/vipcasso-mcp/clearmanagedaccountaiprice.md
- `clearPlatformRateCardItem` — Destructive — https://policylayer.com/tools/vipcasso-mcp/clearplatformratecarditem.md
- `deleteAsset` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deleteasset.md
- `deleteCollection` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletecollection.md
- `deleteCollectionRule` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletecollectionrule.md
- `deleteConciergeLead` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deleteconciergelead.md
- `deleteConciergePersona` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deleteconciergepersona.md
- `deleteConnector` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deleteconnector.md
- `deleteContentLink` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletecontentlink.md
- `deleteContentObject` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletecontentobject.md
- `deletePage` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletepage.md
- `deleteSurface` — Destructive — https://policylayer.com/tools/vipcasso-mcp/deletesurface.md
- `endAccountAccess` — Destructive — https://policylayer.com/tools/vipcasso-mcp/endaccountaccess.md
- `removeCollectionMember` — Destructive — https://policylayer.com/tools/vipcasso-mcp/removecollectionmember.md
- `removeLookFavorite` — Destructive — https://policylayer.com/tools/vipcasso-mcp/removelookfavorite.md
- `removeSiteDomain` — Destructive — https://policylayer.com/tools/vipcasso-mcp/removesitedomain.md
- `removeTeammate` — Destructive — https://policylayer.com/tools/vipcasso-mcp/removeteammate.md
- `revokeApiKey` — Destructive — https://policylayer.com/tools/vipcasso-mcp/revokeapikey.md
- `revokeCollectionShare` — Destructive — https://policylayer.com/tools/vipcasso-mcp/revokecollectionshare.md
- `unpublishCollection` — Destructive — https://policylayer.com/tools/vipcasso-mcp/unpublishcollection.md
- `unpublishPage` — Destructive — https://policylayer.com/tools/vipcasso-mcp/unpublishpage.md
- `unpublishSurface` — Destructive — https://policylayer.com/tools/vipcasso-mcp/unpublishsurface.md
- `executeOperator` — Execute — https://policylayer.com/tools/vipcasso-mcp/executeoperator.md
- `quoteOperatorRun` — Execute — https://policylayer.com/tools/vipcasso-mcp/quoteoperatorrun.md
- `startDirector` — Execute — https://policylayer.com/tools/vipcasso-mcp/startdirector.md
- `startIngestionJob` — Execute — https://policylayer.com/tools/vipcasso-mcp/startingestionjob.md
- `transformAsset` — Execute — https://policylayer.com/tools/vipcasso-mcp/transformasset.md
- `analyzeAsset` — Read — https://policylayer.com/tools/vipcasso-mcp/analyzeasset.md
- `auditionDirectorVoices` — Read — https://policylayer.com/tools/vipcasso-mcp/auditiondirectorvoices.md
- `autoGroupCollections` — Read — https://policylayer.com/tools/vipcasso-mcp/autogroupcollections.md
- …and 202 more: https://policylayer.com/tools/vipcasso-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=vipcasso-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/vipcasso-mcp
