Declare your intention for a resource.
AI agents use log_intent to create or update resources in memro MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your memro MCP Server environment.
The tool appears to write/store an intention declaration for a resource into the memory system. It is a Write operation as it creates a new record. Severity is low since it only logs intent metadata. Confidence is moderate because the description is vague and does not detail what 'resource' means or what side effects may follow.
From the tool's definition 'Declare your intention for a resource' — logs or records an intent, suggesting a write/create operation
Attacks that exploit this kind of access
Declare your intention for a resource. It is categorised as a Write tool in the memro MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the memro MCP Server MCP server in PolicyLayer and add a rule for log_intent: 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 memro MCP Server. Nothing to install.
log_intent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the log_intent 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 log_intent. 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.
log_intent is provided by the memro MCP Server MCP server (memrohq/memro-mcp). 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 →