Get information about available widget types and their properties
AI agents call get-widget-info 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 is a straightforward read operation that retrieves informational data about available widget types and their configurations. It has no side effects, does not modify state, does not execute code or commands, and does not destroy or move data. The blast radius of misuse is minimal—an agent could only retrieve information about widgets that should be documented anyway.
From the tool's definition Tool name 'get-widget-info' and description 'Get information about available widget types and their properties' indicates a retrieval operation that queries metadata about widgets without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get information about available widget types and their properties. 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-widget-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 EuConquisto Composer MCP. Nothing to install.
get-widget-info 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-widget-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.
Set action: deny in the PolicyLayer policy for get-widget-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.
get-widget-info 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 →