get_spatial_tangents
Get the spatial (bezier) in/out tangent handles for all keys of a position (or spatial) property.
This record as markdown: /tools/synthetic-ai-ae-mcp/get-spatial-tangents.md
What get_spatial_tangents does on Ae
AI agents call get_spatial_tangents to retrieve information from Ae 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 |
|---|---|---|---|
compName | string | Yes | |
layerName | string | Yes | |
timeoutMs | number | — | |
projectPath | string | — | |
propertyPath | array | Yes | Property path array, e.g. ['ADBE Transform Group','ADBE Position'] |
Parameters from the server's own tool schema.
Why get_spatial_tangents is rated Low
Even though get_spatial_tangents 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.
Attacks that exploit this kind of access
The rule that runs get_spatial_tangents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ae, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_spatial_tangents, this is the rule to start with:
get_spatial_tangents 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 Ae, apply this rule, and every get_spatial_tangents call is checked against it from then on.
Questions about get_spatial_tangents
Get the spatial (bezier) in/out tangent handles for all keys of a position (or spatial) property. It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.
get_spatial_tangents accepts 5 parameters: compName, layerName, timeoutMs, projectPath, propertyPath. Required: compName, layerName, propertyPath. The full parameter table on this page comes from the server's own tool schema.
Register the Ae MCP server in PolicyLayer and add a rule for get_spatial_tangents: 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 Ae. Nothing to install.
get_spatial_tangents 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_spatial_tangents 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_spatial_tangents. 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_spatial_tangents is provided by the Ae MCP server (@synthetic-ai/ae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ae, and thousands of servers like it.
This server
Across the catalogue