Get settings filtered by a tag key-value pair.
AI agents call get_settings_by_tag to retrieve information from NGS360 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves configuration settings based on tag filtering. It performs a read-only lookup operation on existing settings data, returning filtered results without altering any state, creating resources, executing operations, or deleting data. The minimal blast radius of accidental misuse is querying unintended settings, with no permanent consequences.
From the tool's definition Tool name 'get_settings_by_tag' and description 'Get settings filtered by a tag key-value pair' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get settings filtered by a tag key-value pair. It is categorised as a Read tool in the NGS360 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NGS360 MCP Server MCP server in PolicyLayer and add a rule for get_settings_by_tag: 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 NGS360 MCP Server. Nothing to install.
get_settings_by_tag 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_settings_by_tag 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_settings_by_tag. 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_settings_by_tag is provided by the NGS360 MCP Server MCP server (ngs360/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 →