AI agents call get_record_by_identifier to retrieve information from Devon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single record by its identifier without any side effects. It is a straightforward read operation that queries data without creating, modifying, deleting, or executing any actions. The low severity reflects the minimal risk of misuse—an AI agent retrieving a record causes no damage or unwanted changes to the system.
From the tool's definition Tool name 'get_record_by_identifier' and description 'Get a DEVONthink record using its UUID or ID' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get a DEVONthink record using its UUID or ID. It is categorised as a Read tool in the Devon MCP Server, which means it retrieves data without modifying state.
Register the Devon MCP server in PolicyLayer and add a rule for get_record_by_identifier: 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 Devon. Nothing to install.
get_record_by_identifier 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_record_by_identifier 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_record_by_identifier. 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_record_by_identifier is provided by the Devon MCP server (mnott/devon). 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 →