list_layer_effects

List effects applied to a named layer.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Low RISK CLASS

Category Read

Parameters 42 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/synthetic-ai-ae-mcp/list-layer-effects.md

WHAT IT DOES

What list_layer_effects does on Ae

AI agents call list_layer_effects 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	Composition name.
`layerName`	string	Yes	Layer name.
`timeoutMs`	number	—	Process timeout in milliseconds. Defaults to 120000.
`projectPath`	string	—	Optional absolute path to an .aep file to open first.

Parameters from the server's own tool schema.

RISK

Why list_layer_effects is rated Low

Even though list_layer_effects 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

RECOMMENDED RULE

The rule that runs list_layer_effects 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 list_layer_effects, this is the rule to start with:

list_layer_effects Allowed

list_layer_effects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_layer_effects": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every list_layer_effects call is checked against it from then on.

FAQ

Questions about list_layer_effects

What does the list_layer_effects tool do? +

List effects applied to a named layer. It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.

What parameters does list_layer_effects accept? +

list_layer_effects accepts 4 parameters: compName, layerName, timeoutMs, projectPath. Required: compName, layerName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_layer_effects? +

Register the Ae MCP server in PolicyLayer and add a rule for list_layer_effects: 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.

What risk level is list_layer_effects? +

list_layer_effects is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_layer_effects? +

Yes. Add a rate_limit block to the list_layer_effects 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.

How do I block list_layer_effects completely? +

Set action: deny in the PolicyLayer policy for list_layer_effects. 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.

What MCP server provides list_layer_effects? +

list_layer_effects 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.

KEEP EXPLORING

More on Ae, and thousands of servers like it.

This server

All 226 Ae tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →