restore_post_type_field
Restore a previously deleted field on a post type schema.
This record as markdown: /tools/io-favcrm-favcrm/restore-post-type-field.md
What restore_post_type_field does on FavCRM
AI agents use restore_post_type_field to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
fieldId | string | Yes | Field ID |
postTypeId | string | Yes | Post type ID |
Parameters from the server's own tool schema.
Why restore_post_type_field is rated Medium
This tool modifies data structure reversibly by restoring a previously deleted field. It is Write rather than Destructive because the action is reversible and recovers lost data rather than destroying it. Severity is medium because incorrect restoration could corrupt data schemas or cause application errors, but the operation is confined to schema metadata rather than customer data or financial records.
From the tool's definition Tool name 'restore_post_type_field' and description 'Restore a previously deleted field on a post type schema' indicate the tool modifies schema structure by restoring a deleted field.
Attacks that exploit this kind of access
The rule that runs restore_post_type_field safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restore_post_type_field, this is the rule to start with:
restore_post_type_field 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.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every restore_post_type_field call is checked against it from then on.
Questions about restore_post_type_field
Restore a previously deleted field on a post type schema. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
restore_post_type_field accepts 2 parameters: fieldId, postTypeId. Required: fieldId, postTypeId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for restore_post_type_field: 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 FavCRM. Nothing to install.
restore_post_type_field 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 restore_post_type_field 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 restore_post_type_field. 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.
restore_post_type_field is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue