Log a query for analytics purposes
AI agents use log_query to create or update resources in Rishi's Interactive Resume MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rishi's Interactive Resume MCP Server environment.
This tool writes a log record of a query for analytics tracking. It creates new data (a log entry) but does not delete or execute anything. The blast radius is low since misuse would only result in spurious log entries in an analytics system.
From the tool's definition 'Log a query for analytics purposes' — creates/writes a log entry
Attacks that exploit this kind of access
Log a query for analytics purposes. It is categorised as a Write tool in the Rishi's Interactive Resume MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rishi's Interactive Resume MCP Server MCP server in PolicyLayer and add a rule for log_query: 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 Rishi's Interactive Resume MCP Server. Nothing to install.
log_query 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_query 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_query. 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_query is provided by the Rishi's Interactive Resume MCP Server MCP server (rishia/rishi-resume-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 →