List pending visitors waiting for approval (not yet implemented)
AI agents call ttya_pending to retrieve information from Networkselfmd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays pending visitor data without modifying, deleting, or executing any operations. The word 'List' in the description confirms it is a read-only operation. The note '(not yet implemented)' does not alter the classification.
From the tool's definition Tool name 'ttya_pending' with description 'List pending visitors waiting for approval' indicates a query/retrieval operation that returns a list of pending items with no side effects.
Attacks that exploit this kind of access
List pending visitors waiting for approval (not yet implemented). It is categorised as a Read tool in the Networkselfmd MCP Server, which means it retrieves data without modifying state.
Register the Networkselfmd MCP server in PolicyLayer and add a rule for ttya_pending: 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 Networkselfmd. Nothing to install.
ttya_pending 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 ttya_pending 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 ttya_pending. 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.
ttya_pending is provided by the Networkselfmd MCP server (selfmd/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 →