Look up all SMS opt-in keywords configured in the Postscript account. Returns each keyword
AI agents call get_keyword_id to retrieve information from Postscript without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves keyword configuration data from the Postscript platform without creating, modifying, or deleting any data. It is a read-only lookup operation. The low severity reflects that keyword metadata exposure has minimal blast radius—it does not enable unauthorized subscriber modifications, financial transactions, or destructive actions.
From the tool's definition Tool name 'get_keyword_id' and description 'Look up all SMS opt-in keywords configured in the Postscript account. Returns each keyword' indicate a query/retrieval operation with no modification or execution of external actions.
Attacks that exploit this kind of access
Look up all SMS opt-in keywords configured in the Postscript account. Returns each keyword. It is categorised as a Read tool in the Postscript MCP Server, which means it retrieves data without modifying state.
Register the Postscript MCP server in PolicyLayer and add a rule for get_keyword_id: 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 Postscript. Nothing to install.
get_keyword_id 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_keyword_id 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_keyword_id. 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_keyword_id is provided by the Postscript MCP server (nobanks/postscript-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 →