create_csp
Create a scoped security policy for tenant, team, agent, or user to control tool blocking, execution limits, and approval requirements.
Instructions
Create a contextual security policy with tenant, team, agent or user scope. Read zihin://schemas/csp_config: unknown rule fields may be accepted but have no effect. behavior.must_not_tools blocks named tools; execution ceilings use max_iterations, max_tool_calls and max_tokens_per_request. Native-chat human approval uses require_approval_for with tool names or matchers (tool_name, mcp_server_id, source=mcp|api) and approval_policy_id. Data rules are model instructions, not programmatic masking. origin policies are stored but not enforced; never use them as an access-control boundary. Custom rules become prompt instructions. See zihin://skills/governanca-e-operacao for examples.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"policy_type": "<policy_type>",
"scope": "<scope>",
"rules": "<rules>"
},
"name": "create_csp"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Policy name | |
| rules | Yes | Policy rules; structure depends on the policy type. See zihin://schemas/csp_config. | |
| scope | Yes | Scope where the policy applies | |
| priority | No | Priority; higher values take precedence. Defaults to 0. | |
| exceptions | No | Rule exceptions using the same structure as rules; overrides specific fields | |
| description | No | Policy description | |
| policy_type | Yes | Policy type | |
| scope_target_id | No | Target ID; required for team, agent and user scopes |