Approve an official mirror queue entry without modifying the linked MCP server. This is a synchronous operation. This action: 1. Marks the queue entry as approved 2. Does NOT update the linked MCP server with mirror data 3. Requires the queue entry to already be linked to a server Use this when: ...
AI agents use approve_mirror_no_modify to create or update resources in Pointsyeah — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pointsyeah environment.
This tool modifies data (approval status of a queue entry) in a reversible manner, making it a Write operation rather than Read. The severity is medium because approving queue entries could affect system configuration or workflows, but the impact is limited to metadata state changes without directly executing code or deleting data.
From the tool's definition Marks the queue entry as approved, which modifies the state of a queue entry from pending to approved. This is a state-changing operation that updates administrative metadata.
Attacks that exploit this kind of access
Approve an official mirror queue entry without modifying the linked MCP server. This is a synchronous operation. This action: 1. Marks the queue entry as approved 2. Does NOT update the linked MCP server with mirror data 3. Requires the queue entry to already be linked to a server Use this when: - The queue entry shows an update (pending_update) but you want to acknowledge it without applying changes - The existing server data is correct and doesn. It is categorised as a Write tool in the Pointsyeah MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pointsyeah MCP server in PolicyLayer and add a rule for approve_mirror_no_modify: 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 Pointsyeah. Nothing to install.
approve_mirror_no_modify 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 approve_mirror_no_modify 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 approve_mirror_no_modify. 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.
approve_mirror_no_modify is provided by the Pointsyeah MCP server (slack-workspace-mcp-server). 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 →