get_schema
Return the authoritative JSON Schema for a Clipkit Source — exact field names, types, and enums, generated from the protocol. Call with no argument for the full Source schema, or with element_type (e.g. "text", "shape", "particles") for just that element's fields (much smaller). Use this when aut...
This record as markdown: /tools/dev-clipkit-clipkit/get-schema.md
What get_schema does on Clipkit
AI agents call get_schema to retrieve information from Clipkit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
element_type | string | — | Limit to one element type's fields (e.g. "text"). Omit for the full Source schema (large). |
Parameters from the server's own tool schema.
Why get_schema is rated Low
This tool retrieves schema metadata about Clipkit Sources and their element types. It performs a query operation that returns information without modifying, deleting, or executing any operations. The purpose is purely informational—to help authors understand field names, types, and enums for reference during development. No data is created, modified, deleted, or executed.
From the tool's definition Tool description states 'Return the authoritative JSON Schema' and 'Call with no argument for the full Source schema, or with element_type...for just that element's fields.' The verb 'Return' and action of retrieving/querying schema information indicates a…
Attacks that exploit this kind of access
The rule that runs get_schema safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Clipkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_schema, this is the rule to start with:
get_schema is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Clipkit, apply this rule, and every get_schema call is checked against it from then on.
Questions about get_schema
Return the authoritative JSON Schema for a Clipkit Source — exact field names, types, and enums, generated from the protocol. Call with no argument for the full Source schema, or with element_type (e.g. "text", "shape", "particles") for just that element's fields (much smaller). Use this when authoring with set_project / add_element so you never guess a field. It is categorised as a Read tool in the Clipkit MCP Server, which means it retrieves data without modifying state.
get_schema accepts 1 parameter: element_type. The full parameter table on this page comes from the server's own tool schema.
Register the Clipkit MCP server in PolicyLayer and add a rule for get_schema: 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 Clipkit. Nothing to install.
get_schema is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_schema 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 get_schema. 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.
get_schema is provided by the Clipkit MCP server (https://www.clipkit.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Clipkit, and thousands of servers like it.
This server
Across the catalogue