company_priority_tickets
List a company
This record as markdown: /tools/ai-featureboard-featureboard/company-priority-tickets.md
What company_priority_tickets does on FeatureBoard
AI agents call company_priority_tickets to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why company_priority_tickets is rated Low
The tool lists (retrieves) company-related ticket data. The verb 'List' is a clear indicator of a Read operation. While the description is terse and could be more specific, it unambiguously describes a data retrieval action. There is no indication of modification, deletion, execution, or financial impact.
From the tool's definition Tool name 'company_priority_tickets' and description 'List a company' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs company_priority_tickets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For company_priority_tickets, this is the rule to start with:
company_priority_tickets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every company_priority_tickets call is checked against it from then on.
Questions about company_priority_tickets
List a company. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for company_priority_tickets: 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 FeatureBoard. Nothing to install.
company_priority_tickets 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 company_priority_tickets 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 company_priority_tickets. 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.
company_priority_tickets is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue