ae_get_effect_info

Get information about effects applied to a layer for inspection and debugging

SERVERAe SOURCEae-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ae/ae-get-effect-info.md

WHAT IT DOES

What ae_get_effect_info does on Ae

AI agents call ae_get_effect_info 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.

RISK

Why ae_get_effect_info is rated Low

This tool retrieves information about effects already applied to a layer. The language 'Get information' and explicit mention of 'inspection and debugging' purposes indicate query/inspection operations with no side effects. It does not modify, execute, delete, or move assets—it only reads effect properties for diagnostic purposes.

From the tool's definition Tool name 'ae_get_effect_info' and description 'Get information about effects applied to a layer for inspection and debugging' indicate read-only inspection of existing effect metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ae_get_effect_info Allowed

ae_get_effect_info 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": {
    "ae_get_effect_info": {}
  }
}

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 ae_get_effect_info call is checked against it from then on.

FAQ

Questions about ae_get_effect_info

What does the ae_get_effect_info tool do? +

Get information about effects applied to a layer for inspection and debugging. It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ae_get_effect_info? +

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

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

Can I rate-limit ae_get_effect_info? +

Yes. Add a rate_limit block to the ae_get_effect_info 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 ae_get_effect_info completely? +

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

ae_get_effect_info is provided by the Ae MCP server (ae-mcp-server). 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 35 Ae tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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