Get list of available Composer widgets and their capabilities
AI agents call get-available-widgets to retrieve information from EuConquisto Composer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available widgets without creating, modifying, deleting, or executing anything. It is a straightforward read/retrieval operation with minimal security impact. The low severity reflects that listing widget capabilities poses no risk of data loss, code execution, or financial harm.
From the tool's definition Tool name 'get-available-widgets' and description 'Get list of available Composer widgets and their capabilities' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get list of available Composer widgets and their capabilities. It is categorised as a Read tool in the EuConquisto Composer MCP MCP Server, which means it retrieves data without modifying state.
Register the EuConquisto Composer MCP server in PolicyLayer and add a rule for get-available-widgets: 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 EuConquisto Composer MCP. Nothing to install.
get-available-widgets 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-available-widgets 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-available-widgets. 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-available-widgets is provided by the EuConquisto Composer MCP server (rkm097git/euconquisto-composer-mcp-poc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →