creative_studio_brand_kit_get
Return the loaded brand kit (colours, fonts, logo path, and logo
This record as markdown: /tools/logly-mureo/creative-studio-brand-kit-get.md
What creative_studio_brand_kit_get does on Mureo
AI agents call creative_studio_brand_kit_get to retrieve information from Mureo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why creative_studio_brand_kit_get is rated Low
This is a straightforward data retrieval operation that accesses brand kit metadata for read-only purposes. There are no side effects, no financial impact, no code execution, and no data modification. The blast radius of misuse is minimal — an attacker could learn branding assets but cannot modify campaigns, accounts, or incur spending.
From the tool's definition Tool description states 'Return the loaded brand kit' — retrieves and queries stored configuration data (colours, fonts, logo path). No mutation, deletion, or external operation.
Attacks that exploit this kind of access
The rule that runs creative_studio_brand_kit_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mureo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For creative_studio_brand_kit_get, this is the rule to start with:
creative_studio_brand_kit_get 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 Mureo, apply this rule, and every creative_studio_brand_kit_get call is checked against it from then on.
Questions about creative_studio_brand_kit_get
Return the loaded brand kit (colours, fonts, logo path, and logo. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.
Register the Mureo MCP server in PolicyLayer and add a rule for creative_studio_brand_kit_get: 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 Mureo. Nothing to install.
creative_studio_brand_kit_get 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 creative_studio_brand_kit_get 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 creative_studio_brand_kit_get. 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.
creative_studio_brand_kit_get is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mureo, and thousands of servers like it.
This server
Across the catalogue