AI agents use set_profile_ttl to create or update resources in Ogham — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ogham environment.
This tool creates or modifies data (profile TTL configuration) reversibly—TTL values can be changed again later. It does not delete data irreversibly, execute arbitrary code, or move money. The empty description reduces confidence slightly, but the name and context of a memory management system clearly indicate a Write operation.
From the tool's definition Tool name 'set_profile_ttl' indicates modification of a profile's time-to-live setting. The server manages persistent shared memory with profiles (evidenced by 'list_profiles' and 'current_profile' sibling tools).
Attacks that exploit this kind of access
set_profile_ttl. It is categorised as a Write tool in the Ogham MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ogham MCP server in PolicyLayer and add a rule for set_profile_ttl: 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 Ogham. Nothing to install.
set_profile_ttl 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 set_profile_ttl 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 set_profile_ttl. 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.
set_profile_ttl is provided by the Ogham MCP server (ogham-mcp/ogham-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 →